[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Libtool 1.5.23b

From: Peter O'Gorman
Subject: Re: Libtool 1.5.23b
Date: Mon, 19 Feb 2007 13:07:40 +0900

On Feb 19, 2007, at 8:42 AM, Bill Northcott wrote:

On 19/02/2007, at 4:04 AM, Tim Rice wrote:
Should a single libtool handle both 32bit & 64bit builds on Solaris
with Sun Studio 11?

Is there any support for 64 bit MacOS builds using Apple's -arch option or FSF gcc with -m64?

In particular does it understand that some versions of gcc seem to put 64 bit libs in lib/ppc64 or whatever?

Hi Bill,
libtool-1.5.24 will get the system search paths from gcc, using - print-search-dirs, as it always has, then it will go through the library paths and append whatever $CC $CFLAGS $LDFLAGS -print-multi- directory says. If the directory exists then it will use the multi- directory, if not, it will use the other one.

On darwin, /usr/lib/ppc64 /usr/local/lib/ppc64 etc do not normally exist, so they will not be added. Here is an example:
$ ./configure CFLAGS="-Os -m64"
$ grep ^sys_lib_search_path_spec libtool
sys_lib_search_path_spec="/usr/lib/gcc/powerpc-apple-darwin8/4.0.1/ ppc64 /usr/lib /usr/local/lib"

$ ./configure CFLAGS="-Os"
$ grep ^sys_lib_search_path_spec libtool
sys_lib_search_path_spec="/usr/lib/gcc/powerpc-apple-darwin8/4.0.1 / usr/lib /usr/local/lib"

Any library paths that you specify with -L will not get this treatment though. If you're building for a prefix outside of /usr or / usr/local and you want this behavior, you should export LIBRARY_PATH~ $prefix/lib before configure and that path will be treated like a system search path.

Hope that this helps,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]