Re: Extend libtool dll namespaces for mingw-w64

2010-01-30 Thread JonY
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

2010-01-30 Thread Ralf Wildenhues
* 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

2010-01-30 Thread Dave Korn
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

2010-01-30 Thread JonY
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

2010-01-30 Thread Ralf Wildenhues
* 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

2010-01-30 Thread Roumen Petrov
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

2010-01-30 Thread Tor Lillqvist
> 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

2010-01-30 Thread JonY
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: silent installs

2010-01-30 Thread Ralf Wildenhues
[ moving to libtool@ from automake@; this is this particular message is about whether the relinking warning and the warning about the need to --finish should be changed to be notices only, which would cause th