Re: On Windows, $old_archive_cmds uses `lib' to create static archives.

Quoting Ralf Wildenhues <[EMAIL PROTECTED]>: * Benoit Sigoure wrote on Sun, Apr 22, 2007 at 07:42:24PM CEST: On Windows, when compiling with Visual C++, libtool seems to figure out automagically that it has to create static archives with the `lib' command. [...] I wonder how libtool figured t

Re: On Windows, $old_archive_cmds uses `lib' to create static archives.

* Benoit Sigoure wrote on Sun, Apr 22, 2007 at 07:42:24PM CEST: > > On Windows, when compiling with Visual C++, libtool seems to figure out > automagically that it has to create static archives with the `lib' command. [...] > I wonder how libtool figured this out and why libtool does this since it

Re: libtool/ltmain linking wrong (/usr/lib) libstdc++

Hello Liviu, Thanks for the report. * Liviu Nicoara wrote on Fri, Apr 20, 2007 at 04:50:46PM CEST: > > I am trying to link a library and test program in an autotools-based > project using Intel C++ 9.1.042 and GCC 4.1.2. > > One of my machines has a default installation of GCC (3.3.6). I built an

On Windows, $old_archive_cmds uses `lib' to create static archives.

Hello list, On Windows, when compiling with Visual C++, libtool seems to figure out automagically that it has to create static archives with the `lib' command. Here is a line of the libtool script: old_archive_cmds="lib /OUT:\$oldlib\$oldobjs\$old_deplibs" I wonder how libtool figured this out a

Re: libstdc++.la listed in dependency_libs of a static C++ library?

Quoting Benoit Sigoure <[EMAIL PROTECTED]>: Quoting Ralf Wildenhues <[EMAIL PROTECTED]>: That's not the only (or important, FWIW) issue here, though. The installed libstdc++.la file is broken. Reason for that include bugs/limitations in Libtool, bugs in GCC, and possibly in the script that ha