Re: MS lib program in msys
Ralf Wildenhues wrote: Hello Christopher, Thanks for the report. * Christopher Hulbert wrote on Fri, Jan 05, 2007 at 04:10:18PM CET: Libtool uses MS's lib program when not using gcc in windows. On msys "lib /out:.libs/liba.lib" is translated to "lib C:\msys1.0\OUT;.libs\liba.lib". I'm not sure when lib (or windows) started accepting "-" for options, but "lib -out" fixes the problem on Windows XP. Would there be any objection to changing that in mainline libtool? I think that when we put that in, there were some older MSVC versions that did no accept -out. May be remembering wrongly, though. Pretty sure "-" has been valid since at least Win95. Definitely this should be changed. [EMAIL PROTECTED] ~ $ lib /OUT:.libs/liba.lib Microsoft (R) Library Manager Version 7.10.3077 Copyright (C) Microsoft Corporation. All rights reserved. LIB : fatal error LNK1104: cannot open file 'C:\msys1.0\OUT;.libs\liba.lib' Does lib //OUT:.libs/liba.lib work? Does anybody know whether doubling the slash can lead to problems when used under Cygwin (I think they address shares that way)? Not that the Cygwin/MSVC combo works with Libtool now... On MSYS //foo becomes /foo, so it would work. On Cygwin //foo is left alone, so it would not work. Please just change everything to use dashes. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sunhttp://highlandsun.com/hyc OpenLDAP Core Teamhttp://www.openldap.org/project/ ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: MS lib program in msys
On 1/8/07, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: Hello Christopher, Thanks for the report. * Christopher Hulbert wrote on Fri, Jan 05, 2007 at 04:10:18PM CET: > Libtool uses MS's lib program when not using gcc in windows. On msys > "lib /out:.libs/liba.lib" is translated to "lib > C:\msys1.0\OUT;.libs\liba.lib". I'm not sure when lib (or windows) > started accepting "-" for options, but "lib -out" fixes the problem on > Windows XP. Would there be any objection to changing that in mainline > libtool? I think that when we put that in, there were some older MSVC versions that did no accept -out. May be remembering wrongly, though. What about a libtool autoconf test for lib -out and if that fails use lib /out? I'm tied up monday and tuesday, but I can try to write that patch after that to test the concept. Chris > [EMAIL PROTECTED] ~ > $ lib /OUT:.libs/liba.lib > Microsoft (R) Library Manager Version 7.10.3077 > Copyright (C) Microsoft Corporation. All rights reserved. > > LIB : fatal error LNK1104: cannot open file 'C:\msys1.0\OUT;.libs\liba.lib' Does lib //OUT:.libs/liba.lib work? Does anybody know whether doubling the slash can lead to problems when used under Cygwin (I think they address shares that way)? Not that the Cygwin/MSVC combo works with Libtool now... Nope. [EMAIL PROTECTED] ~]$ lib //OUT:.libs/liba.lib Microsoft (R) Library Manager Version 8.00.50727.42 Copyright (C) Microsoft Corporation. All rights reserved. LIB : warning LNK4044: unrecognized option '//OUT:.libs/liba.lib'; ignored Thanks, Ralf ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: MS lib program in msys
Hello Christopher, Thanks for the report. * Christopher Hulbert wrote on Fri, Jan 05, 2007 at 04:10:18PM CET: > Libtool uses MS's lib program when not using gcc in windows. On msys > "lib /out:.libs/liba.lib" is translated to "lib > C:\msys1.0\OUT;.libs\liba.lib". I'm not sure when lib (or windows) > started accepting "-" for options, but "lib -out" fixes the problem on > Windows XP. Would there be any objection to changing that in mainline > libtool? I think that when we put that in, there were some older MSVC versions that did no accept -out. May be remembering wrongly, though. > [EMAIL PROTECTED] ~ > $ lib /OUT:.libs/liba.lib > Microsoft (R) Library Manager Version 7.10.3077 > Copyright (C) Microsoft Corporation. All rights reserved. > > LIB : fatal error LNK1104: cannot open file 'C:\msys1.0\OUT;.libs\liba.lib' Does lib //OUT:.libs/liba.lib work? Does anybody know whether doubling the slash can lead to problems when used under Cygwin (I think they address shares that way)? Not that the Cygwin/MSVC combo works with Libtool now... Thanks, Ralf ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: no .so file on HPUX platform?
Hello Ed, * Ed Hartnett wrote on Wed, Jan 03, 2007 at 05:50:38PM CET: > > On our HPUX platform however, no libnetcdf.so file results. Yet the > build seems to work OK. The shared library extension should be '.sl'. Please show ./libtool --config and ./libtool --features It seems like shared libs were disabled in your configure for some reason, after the normal libtool setup junk. Does your package use the file config.rpath (i.e., is it present anywhere in the source tree)? There may be a related bug if you do. Cheers, and a happy New Year, Ralf ___ http://lists.gnu.org/mailman/listinfo/libtool
