[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to force -liberty?
From: |
Glynn Clements |
Subject: |
Re: How to force -liberty? |
Date: |
Fri, 30 Jul 2004 01:58:34 GMT |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Security Through Obscurity) |
"Kilian A. Foth" <foth@informatik.uni-hamburg.de> writes:
> I'm trying to compile a largish autoconf'ed project (KDE) on an
> outlandish platform (Solaris) and working around many Linuxisms in the
> sources. The latest one has me stumped: files use vasprintf() under the
> assumption that this would be provided by the standard libraries, but
> on Solaris it isn't. That would be no big problem; I know that
> linking to libiberty fixes that, but I can't for the life of me figure
> out where to put the `-liberty' to that the build process picks it up.
>
> The usual solutions of adding it to CXXFLAGS, to the Makefile etc.
> don't work. I even ran amok and hacked the local libtool to include it
> unconditionally -- no success. How do I tell the autoconf system "Yes,
> I do need libiberty unconditionally!' ?
CFLAGS/CXXFLAGS are used for compiling, not linking. For linking, you
could try using LDFLAGS or LIBS; autoconf will set these variables
from the environment in a similar manner to CFLAGS/CXXFLAGS.
--
Glynn Clements <glynn.clements@virgin.net>