From: Emanuel F. <E.F...@op...> - 2014-12-12 02:42:30
|
Hello, Apologies for breaking in, but I take a slight offence at the following statement: > Whoever mixes MinGW and MinGW64 programs on his/her machine is playing with fire. Most of us here are programmers and I reckon that many (if not most) of us write programs for third parties, like us. Due to the extremely various environments of our clients, we simply MUST "mix MinGW and MinGW64 programs on [our] machine[s]": we have no choice! To illustrate, one of our huge clients simply won't upgrade from Java 6.24 32 bits in foreseeable future (for "security reasons", I guess), while others are on Java 7 64 bits since ages - any DLL with JNA we produce MUST therefore be available in both bitnesses. Now "playing with fire" it was indeed, to set up everything to be able to make (and run) both versions without problems... but it should not have been. On 11-Dec-14 04:56, Yongwei Wu wrote: > (Wrongly replied to only Eli previously.) > > On 10 December 2014 at 00:32, Eli Zaretskii <el...@gn...> wrote: >>> Date: Tue, 9 Dec 2014 17:30:10 +0800 >>> From: Yongwei Wu <wuy...@gm...> >>> >>> I think the name libstdc++.dll is also a little problematic, as it >>> hides the ABI and runtime differences. The Cygwin DLL name >>> cygstdc++-6.dll is better >> You are confusing the name of the DLL with the name of its import >> library. The former is called libstdc++-6.dll in MinGW; the latter is >> libstdc++.dll.a, and has no version in its name. There's no reason to >> have a version in the import library's name, because you are supposed >> to develop against a single version at a time. The DLLs, OTOH, can >> and should have versions, because different programs can depend on >> different versions. > No, I was not. I cared only about the DLLs, but not the import > libraries (your misunderstanding might be caused by my typo: I missed > "-6" once). A stray import library does not cause harm, unless one put > into the MinGW directory. I do not suppose people would be doing that. > >>> but even mgwstdc++.dll will not be good enough, as there is the >>> SJLJ/DW2 difference and winthread/pthread difference on >>> Windows. However, I would think naming MinGW DLLs mgw* a good start, >>> as the official MinGW distribution is consistent on the variants I >>> mentioned. People using MinGW variants should give their DLLs a >>> different prefix. >> Whoever mixes MinGW and MinGW64 programs on his/her machine is playing >> with fire. > Even if I did not install them both, some programs might come with a > libstdc++-6.dll from the MinGW version he used. The disaster would > then follow either because the installation path is added to the > system PATH or user PATH, or because libstdc++-6.dll is copied to a > system directory (as the OP encountered). > > I do have two conflicting libstdc++-6.dll on our my system (though > only one in the system path). It would be better if we avoided it > proactively. > > -- > Wu Yongwei > URL: http://wyw.dcweb.cn/ > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. Disregard for the list etiquette may cause your account to be moderated. > > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > Also: mailto:min...@li...?subject=unsubscribe --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com |