On 19/02/2007, at 3:07 PM, Peter O'Gorman wrote:
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?
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"
[snip]
$ 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"
This seems to be the sort of result I want. I presume this is in the
1.5.23b.
Because I am on a Mac, I am using Apple's gcc for C and C++ with a
gfortran from hpc.sourceforge.net. It is the latter that is putting
its non-fat 64 bit libs in /usr/local/lib/ppc64. Apple's libs in /
usr/lib are all fat.
Print search dirs gives:
[PM-G5BN:~] billn% /usr/local/bin/gfortran -m64 -print-search-dirs
install: /usr/local/lib/gcc/powerpc-apple-darwin8.8.0/4.3.0/
programs: =/usr/local/libexec/gcc/powerpc-apple-darwin8.8.0/4.3.0/:/
usr/local/libexec/gcc/powerpc-apple-darwin8.8.0/4.3.0/:/usr/local/
libexec/gcc/powerpc-apple-darwin8.8.0/:/usr/local/lib/gcc/powerpc-
apple-darwin8.8.0/4.3.0/:/usr/local/lib/gcc/powerpc-apple-
darwin8.8.0/:/usr/libexec/gcc/powerpc-apple-darwin8.8.0/4.3.0/:/usr/
libexec/gcc/powerpc-apple-darwin8.8.0/:/usr/lib/gcc/powerpc-apple-
darwin8.8.0/4.3.0/:/usr/lib/gcc/powerpc-apple-darwin8.8.0/:/usr/local/
lib/gcc/powerpc-apple-darwin8.8.0/4.3.0/../../../../powerpc-apple-
darwin8.8.0/bin/powerpc-apple-darwin8.8.0/4.3.0/:/usr/local/lib/gcc/
powerpc-apple-darwin8.8.0/4.3.0/../../../../powerpc-apple-darwin8.8.0/
bin/
libraries: =/usr/local/lib/gcc/powerpc-apple-darwin8.8.0/4.3.0/
ppc64/:/usr/lib/gcc/powerpc-apple-darwin8.8.0/4.3.0/ppc64/:/usr/local/
lib/gcc/powerpc-apple-darwin8.8.0/4.3.0/../../../../powerpc-apple-
darwin8.8.0/lib/powerpc-apple-darwin8.8.0/4.3.0/ppc64/:/usr/local/lib/
gcc/powerpc-apple-darwin8.8.0/4.3.0/../../../../powerpc-apple-
darwin8.8.0/lib/ppc64/:/usr/local/lib/gcc/powerpc-apple-
darwin8.8.0/4.3.0/../../../powerpc-apple-darwin8.8.0/4.3.0/ppc64/:/
usr/local/lib/gcc/powerpc-apple-darwin8.8.0/4.3.0/../../../ppc64/:/
lib/powerpc-apple-darwin8.8.0/4.3.0/ppc64/:/lib/ppc64/:/usr/lib/
powerpc-apple-darwin8.8.0/4.3.0/ppc64/:/usr/lib/ppc64/:/usr/local/lib/
gcc/powerpc-apple-darwin8.8.0/4.3.0/:/usr/lib/gcc/powerpc-apple-
darwin8.8.0/4.3.0/:/usr/local/lib/gcc/powerpc-apple-
darwin8.8.0/4.3.0/../../../../powerpc-apple-darwin8.8.0/lib/powerpc-
apple-darwin8.8.0/4.3.0/:/usr/local/lib/gcc/powerpc-apple-
darwin8.8.0/4.3.0/../../../../powerpc-apple-darwin8.8.0/lib/:/usr/
local/lib/gcc/powerpc-apple-darwin8.8.0/4.3.0/../../../powerpc-apple-
darwin8.8.0/4.3.0/:/usr/local/lib/gcc/powerpc-apple-
darwin8.8.0/4.3.0/../../../:/lib/powerpc-apple-darwin8.8.0/4.3.0/:/
lib/:/usr/lib/powerpc-apple-darwin8.8.0/4.3.0/:/usr/lib/
which sort of seems right.
Is the libgfortran likely to picked up correctly when linking C code
with a Fortran library? or is this a case which is not supported?
Thanks
Bill
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
