Re: Extend libtool dll namespaces for mingw-w64

On Tue, Jan 26, 2010 at 5:26 PM, JonY wrote: > Hi, > > Currently, on Win32 platforms, Cygwin uses the "cyg" prefix for dlls, > and MinGW based systems uses the "lib" prefix. > > This works fine, until mingw-w64 showed up with 64bit dlls. This > problem is especially apparent with trying to build m

Re: Extend libtool dll namespaces for mingw-w64

On 1/26/2010 23:52, Alon Bar-Lev wrote: On Tue, Jan 26, 2010 at 5:26 PM, JonY wrote: Hi, Currently, on Win32 platforms, Cygwin uses the "cyg" prefix for dlls, and MinGW based systems uses the "lib" prefix. This works fine, until mingw-w64 showed up with 64bit dlls. This problem is especially

Re: Extend libtool dll namespaces for mingw-w64

On Tue, 26 Jan 2010, Alon Bar-Lev wrote: libtool should also check if GCC "-m32" or "-m64" is used, and select the proper namespace accordingly (mingw-w64 GCC can do multilib). Comments? This is highly none standard naming convention... Handling w32 and w64 should be the same as handling mul

Re: Extend libtool dll namespaces for mingw-w64

Den 2010-01-26 16:26 skrev JonY: I suggest the following naming scheme. mingw.org:lib-.dll (unchanged) Cygwin:cyg-.dll (unchanged) mingw-w64(64):lib64-.dll mingw-w64(32):lib32-.dll But then mingw-w64 invades the mingw.org namespace. Perhaps l64-.dll and l32-.dll? Cheers, P

Re: Extend libtool dll namespaces for mingw-w64

On 1/27/2010 18:02, Peter Rosin wrote: Den 2010-01-26 16:26 skrev JonY: I suggest the following naming scheme. mingw.org: lib-.dll (unchanged) Cygwin: cyg-.dll (unchanged) mingw-w64(64): lib64-.dll mingw-w64(32): lib32-.dll But then mingw-w64 invades the mingw.org namespace. Perhaps l64-.dll

Re: Extend libtool dll namespaces for mingw-w64

On Tue, 2010-01-26 at 23:26 +0800, JonY wrote: ... > I suggest the following naming scheme. > > mingw.org:lib-.dll (unchanged) > Cygwin: cyg-.dll (unchanged) > mingw-w64(64):lib64-.dll > mingw-w64(32):lib32-.dll > > libtool should also check if GCC "-m32" or "-m6

Re: Extend libtool dll namespaces for mingw-w64

Den 2010-01-27 20:54 skrev Matěj Týč: On Tue, 2010-01-26 at 23:26 +0800, JonY wrote: ... I suggest the following naming scheme. mingw.org: lib-.dll (unchanged) Cygwin: cyg-.dll (unchanged) mingw-w64(64): lib64-.dll mingw-w64(32): lib32-.dll libtool should also check if GCC "-m32

Re: Extend libtool dll namespaces for mingw-w64

On Wed, 2010-01-27 at 22:19 +0100, Peter Rosin wrote: > Den 2010-01-27 20:54 skrev Matěj Týč: > > On Tue, 2010-01-26 at 23:26 +0800, JonY wrote: > > ... > >> I suggest the following naming scheme. > >> > >> mingw.org: lib-.dll (unchanged) > >> Cygwin:cyg-.dll (unchanged) > >> mingw-w64(

Re: Extend libtool dll namespaces for mingw-w64

Matěj Týč wrote: On Tue, 2010-01-26 at 23:26 +0800, JonY wrote: ... I suggest the following naming scheme. mingw.org: lib-.dll (unchanged) Cygwin: cyg-.dll (unchanged) mingw-w64(64): lib64-.dll mingw-w64(32): lib32-.dll libtool should also check if GCC "-m32" or "-m64" is used,

Re: Extend libtool dll namespaces for mingw-w64

Matěj Týč wrote: [SNIP] Wow, this is interesting. I remember that one guy asked about the dll prefix and he has been advised to strip the prefix from the library name and add the '-module' flag to libtool in order to silence complaints. [SNIP] -module flag will install dll in $libdir and without

Re: Extend libtool dll namespaces for mingw-w64

> I'm not sure that idea for lib{64|32} is so good. Me neither, but, > As I know for 32 bit process  64 bit microsoft windows os will return > %WINDOWS%\SysWOW64 as system folder. For 64 bit process it is > %WINDOWS%\System32 I fail to see what *that* has to do with it. Surely nobody builds any

Re: Extend libtool dll namespaces for mingw-w64

* JonY wrote on Tue, Jan 26, 2010 at 04:26:32PM CET: > Currently, on Win32 platforms, Cygwin uses the "cyg" prefix for dlls, > and MinGW based systems uses the "lib" prefix. > > This works fine, until mingw-w64 showed up with 64bit dlls. This > problem is especially apparent with trying to build m

Re: Extend libtool dll namespaces for mingw-w64

On 1/28/2010 13:46, Ralf Wildenhues wrote: * JonY wrote on Tue, Jan 26, 2010 at 04:26:32PM CET: Currently, on Win32 platforms, Cygwin uses the "cyg" prefix for dlls, and MinGW based systems uses the "lib" prefix. This works fine, until mingw-w64 showed up with 64bit dlls. This problem is especi

Re: Extend libtool dll namespaces for mingw-w64

> The issue is that libtool > uses the "lib" prefix for both 64bit and 32bit DLLs, and for both mingw > and mingw-w64. Well, my take is that except for people working on the *tools themselves* (meaning gcc, binutils etc), this is not really a problem. Sure, libtool is a tool used by developers, bu

Re: Extend libtool dll namespaces for mingw-w64

On 1/28/2010 19:30, Tor Lillqvist wrote: The issue is that libtool uses the "lib" prefix for both 64bit and 32bit DLLs, and for both mingw and mingw-w64. Well, my take is that except for people working on the *tools themselves* (meaning gcc, binutils etc), this is not really a problem. Sure, li

Re: Extend libtool dll namespaces for mingw-w64

[ Dave, this is ; see at the end for a quick GCC-related question ] Hello, first off, I completely agree with Tor's reply to your message. Adding a couple of bits: * JonY wrote on Thu, Jan 28, 2010 at 11:06:50AM CET: > On 1/28/201

Re: Extend libtool dll namespaces for mingw-w64

On 1/29/2010 04:07, Ralf Wildenhues wrote: My proposal has the same rationale as using the "cyg" and "lib" prefix on Cygwin and MinGW, so no DLLs can clash. No, that is not the same thing. The Cygwin runtime system actually looks for libraries named cyg.dll; see 'info ld WIN32'. The GNU libc

Re: Extend libtool dll namespaces for mingw-w64

On Fri, 29 Jan 2010, JonY wrote: Another solution it to stop installing DLLs to bindir and follow unix style installs into libdir, right beside the import libs, let the user set the PATH. That way, we don't need a bin32 and bin64 directory, but it does not prevent possible conflicts with 32bit m

Re: Extend libtool dll namespaces for mingw-w64

On 1/29/2010 10:29, Bob Friesenhahn wrote: On Fri, 29 Jan 2010, JonY wrote: Another solution it to stop installing DLLs to bindir and follow unix style installs into libdir, right beside the import libs, let the user set the PATH. That way, we don't need a bin32 and bin64 directory, but it does

Re: Extend libtool dll namespaces for mingw-w64

On 29/01/2010 01:10, JonY wrote: > On 1/29/2010 04:07, Ralf Wildenhues wrote: > Yes, GCC trunk uses that, but right now, -bindir for both 32bit and > 64bit subsystems point to the same dir. > > Another solution it to stop installing DLLs to bindir and follow unix > style installs into libdir, rig

Re: Extend libtool dll namespaces for mingw-w64

On 1/29/2010 20:16, Dave Korn wrote: So I think what I'd conclude is that MinGW-W64 should have its own prefix, but it should be the same one for 32-bit and 64-bit W64 DLLs. Hi, I'm not entirely sure how to avoid 64bit vs 32bit mingw-w64 clashing if both use the same DLL naming scheme.

Re: Extend libtool dll namespaces for mingw-w64

Hi Dave, thanks for the feedback. * Dave Korn wrote on Fri, Jan 29, 2010 at 01:16:37PM CET: > This is GCC PR40125, and I don't suppose I'm going to be able to fix it > before 4.5.0. Kai suggested we should leave them in gcc's private dir (which > is where the language runtime import libs go, n

Re: Extend libtool dll namespaces for mingw-w64

On 1/30/2010 06:55, Ralf Wildenhues wrote: That would be fine with me. But I suggest that any policy decision for such a naming change should be done by those projects (MinGW-W64, MinGW, or both), documented there, a flag day announced, and then libtool should follow suit, not the other way rou

Re: Extend libtool dll namespaces for mingw-w64

* JonY wrote on Sat, Jan 30, 2010 at 10:47:11AM CET: > On 1/30/2010 06:55, Ralf Wildenhues wrote: > > > >That would be fine with me. But I suggest that any policy decision for > >such a naming change should be done by those projects (MinGW-W64, MinGW, > >or both), documented there, a flag day anno

Re: Extend libtool dll namespaces for mingw-w64

On 30/01/2010 14:56, Ralf Wildenhues wrote: > web site, refer to this page, rebuild your binutils ld to automatically > search for the changed prefix when it encounters -lfoo on the command Not binutils, I don't think: > [1] My ld.info contains, speaking about cygwin, > > For instance, w

Re: Extend libtool dll namespaces for mingw-w64

On 1/30/2010 22:56, Ralf Wildenhues wrote: If any of the Libtool users come and complain about libtool not linking against their old (or new) libraries after we've made the change, I want to be able to point to your documentation site and tell them "we had no choice, upstream had a flag day, tou

Re: Extend libtool dll namespaces for mingw-w64

* JonY wrote on Sat, Jan 30, 2010 at 05:29:31PM CET: > I misunderstood one of the users who was testing an XP 64bit, it seems > that it does not skip incompatible DLLs like Vista or 7. After some > confirmation, its clear that XP64 does skip properly, so maybe having > the same prefix for 64bit/32b

Re: Extend libtool dll namespaces for mingw-w64

I don't understand request as the usually final result is .../libfool.la .../libfool.dll.a .../libfool.dll .../libfool.a Also note that makefiles the macros(variables) are libfoo_. Did the requester expect if target is libfoo_ make command to search for libYYfoo_ or may be requeste

Re: Extend libtool dll namespaces for mingw-w64

> That is just not sane engineering practice. > I'd even consider > installing 64bit packages in a separate --prefix from 32bit ones to be > good packaging practice, > GCC is a *special* case, to be fixed in the GCC package. Don't confuse > the compiler+tools special cases with the rest of norma

Re: Extend libtool dll namespaces for mingw-w64

On 1/31/2010 02:14, Roumen Petrov wrote: I don't understand request as the usually final result is .../libfool.la .../libfool.dll.a .../libfool.dll .../libfool.a Also note that makefiles the macros(variables) are libfoo_. Did the requester expect if target is libfoo_ make command to sear

Re: Extend libtool dll namespaces for mingw-w64

JonY wrote: On 1/31/2010 02:14, Roumen Petrov wrote: I don't understand request as the usually final result is .../libfool.la .../libfool.dll.a .../libfool.dll .../libfool.a Also note that makefiles the macros(variables) are libfoo_. Did the requester expect if target is libfoo_ make co

Re: Extend libtool dll namespaces for mingw-w64

On 2/1/2010 01:18, Roumen Petrov wrote: JonY wrote: On 1/31/2010 02:14, Roumen Petrov wrote: I don't understand request as the usually final result is .../libfool.la .../libfool.dll.a .../libfool.dll .../libfool.a Also note that makefiles the macros(variables) are libfoo_. Did the requeste