ICC Compilers on Linux
Hi all, What is the status of libtool support for the icc compiler on Linux? Right now, it causes a problem because the "wl" variable in the generated libtool file should be set to "-Wl," instead of "", which is what it currently does. I tried it with libtool 1.4.3 and autoconf 2.56 (2.57 didn't work for me) and it still had a problem. Is there someone working on this? Thanks! -- || Bill Wendling"Real Programmers have a Snoopy Calendar || [EMAIL PROTECTED]of '69 hanging on their wall" || Coding Simian -- Toon Moene ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Re: ICC Compilers on Linux
Bill, There is no support for icc in 1.4.3, but there is support in CVS Libtool. Robert Bill Wendling wrote: > > Hi all, > > What is the status of libtool support for the icc compiler on Linux? > Right now, it causes a problem because the "wl" variable in the generated > libtool file should be set to "-Wl," instead of "", which is what it > currently does. I tried it with libtool 1.4.3 and autoconf 2.56 (2.57 > didn't work for me) and it still had a problem. > > Is there someone working on this? > > Thanks! > > -- > || Bill Wendling"Real Programmers have a Snoopy Calendar > || [EMAIL PROTECTED]of '69 hanging on their wall" > || Coding Simian -- Toon Moene > > ___ > Libtool mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/libtool ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
bash versus printf -exported_symbol on OSF
For cxx on "osf4* | osf5*", libtool uses printf "-exported_symbol " as part of archive_expsym_cmds. Unfortunately bash 2.05b objects to this with printf: -e: invalid option The bash doco doesn't mention any options for printf, but I suppose it parses them in the usual way. Unlike /usr/bin/printf on OSF, which is happy just to print "-exported..." Using "printf -- -exported_symbol " seems to work with both bash and /usr/bin/printf. Unless anyone knows better perhaps this would be a good change. ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Re: bash versus printf -exported_symbol on OSF
I wrote: > > Using "printf -- -exported_symbol " seems to work with both bash and > /usr/bin/printf. Unless anyone knows better perhaps this would be a > good change. Ah, sorry, I just tried "dash", the Almquist shell on Debian, and its builtin gives "--" for "printf --". A better way to avoid any doubt might be printf "%cexported_symbol " - ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Re: bash versus printf -exported_symbol on OSF
Kevin Ryde wrote: > > I wrote: > > > > Using "printf -- -exported_symbol " seems to work with both bash and > > /usr/bin/printf. Unless anyone knows better perhaps this would be a > > good change. > > Ah, sorry, I just tried "dash", the Almquist shell on Debian, and its > builtin gives "--" for "printf --". A better way to avoid any doubt > might be > > printf "%cexported_symbol " - Any particular problem with: echo '-exported_symbol ' ??? I would favor not supporting a shell that has an echo that doesn't print all its arguments. (Only excepting the two character argument strings, "-n", "-e" and "-E" because of an historical mistake.) ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Re: bash versus printf -exported_symbol on OSF
Bruce Korb <[EMAIL PROTECTED]> writes: > > Any particular problem with: > > echo '-exported_symbol ' Offhand I can't give an example problem, but autoconf "Limitations of Builtins" specifically advises against trying to echo anything starting with "-". ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Problem with libtool
Hi, When trying to build some apps, I got this : [...] checking dynamic linker characteristics... Linux ld.so checking if libtool supports shared libraries... yes *** Warning: the command libtool uses to detect shared libraries, *** /usr/bin/file, produces output that libtool cannot recognize. *** The result is that libtool may fail to recognize shared libraries *** as such. This will affect the creation of libtool libraries that *** depend on shared libraries, but programs linked with such libtool *** libraries will work regardless of this problem. Nevertheless, you *** may want to report the problem to your system manager and/or to *** [EMAIL PROTECTED] checking whether to build shared libraries... yes checking whether to build static libraries... yes [...] Nothing is in the config.log file about this... I have compiled the last libtool (1.4.3). The 'file' command is located at /usr/local/bin on my system. I don't see where the problem can be... It would be great if you could help me with this ! Best regards, Pierre. ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
