* Ethan Mallove wrote on Fri, Dec 10, 2010 at 07:41:20PM CET:
> On Thu, Oct/21/2010 06:13:03AM, Ralf Wildenhues wrote:
> > Pass -Wc,-static-intel instead.
>
> This works like a charm for shared libraries, but for standalone
> executables I get an error like this:
>
> ...
> icc: command line warning #10156: ignoring option '-W'; no argument required
> /bin/sh ../../../libtool --tag=CC --mode=link icc -Wc,-static-intel -g
> -finline-functions -fno-strict-aliasing -restrict -pthread
> -fvisibility=hidden -export-dynamic -o orte-iof orte-iof.o
> ../../../orte/libopen-rte.la -lnsl -lutil
> libtool: link: icc -Wl,-static-intel -g -finline-functions
> -fno-strict-aliasing -restrict -pthread -fvisibility=hidden -o .libs/orte-iof
> orte-iof.o -Wl,--export-dynamic ../../../orte/.libs/libopen-rte.so -ldl
> -lnsl -lutil -pthread -Wl,-rpath -Wl,$ORIGIN -Wl,-rpath -Wl,$ORIGIN/..
> -Wl,-rpath -Wl,$ORIGIN/../lib
> ipo: warning #11015: Warning unknown option -static-intel
> ld: unrecognized -a option `tic-intel'
>
> Do you know of a way to get this working in both cases: shared libs
> and standalone executable?
Yes. Use Libtool 2.2.8 or newer. Quoting from the NEWS file:
- Fix ancient bug where "-Wc," was turned into "$wl" (typically "-Wl,")
when using the compiler driver to link programs. Now "-Wc," is stripped
just as it is when linking libraries through the compiler driver.
Cheers,
Ralf
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
