[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LT 1.5: problem with Solaris Forte 64 bit shared C++ libraries
From: |
Jeff Squyres |
Subject: |
Re: LT 1.5: problem with Solaris Forte 64 bit shared C++ libraries |
Date: |
Sat, 3 May 2003 13:19:04 -0400 (EDT) |
On Sat, 3 May 2003, Bob Friesenhahn wrote:
> > True. But will libtool pass these flags through? I'm ok telling
>
> The intention is that libtool will pass these flags through. Alas, I
> have noticed that things can get complicated since Autoconf's configure
> and libtool may not agree on how the flags are passed and what works
> with libtool may fail entirely with configure.
Invoking libtool manually with:
-----
shell% /bin/bash ./libtool --mode=link CC <FLAGS> -o liblibtool_test.la -rpath
/usr/local/lib foo.lo bar.lo
-----
and substituting in various things for <FLAGS>, I can't seem to get
anything passed down to the actual linker command line that works --
libtool strips them all out. Partial list of things that I've tried:
-xarch=v9
-z -xarch=v9
-64
"-Wl,-xarch=v9" does get passed down, but CC doesn't recognize -Wl (-Wl is
apparently an option for cc, not CC).
Is there any other way to pass things down magically to libtool's
invocation line?
> The fundamental problem is that while Autoconf has CXX, CFLAGS, LDFLAGS,
> & LIBS nicely seperated into different shell variables so it knows their
> intended application, libtool must receive the options on its command
> line and correctly inuit their purpose, passing them in the correct
> order to the correct tool.
Understood.
--
{+} Jeff Squyres
{+} address@hidden
{+} http://www.lam-mpi.org/