Geoff,
I am still puzzled by your statement that ".1.dylib files should never be
used
directly in a link". With both gcc trunk and Xcode 2.3, the following...
[Jack-Howarths-Computer:~] howarth% gcc -O3 -m64 modulo.c -shared-libgcc
[Jack-Howarths-Computer:~] howarth% otool64 -L ./a.out
./a.out:
/usr/lib/libgcc_s_ppc64.1.dylib (compatibility version 1.0.0, current
version 1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 88.1.6)
links against the *.1.dylib version of the shared library. Also the *.1.dylib
versions
of libgcc_s are the only shared library versions available. Lastly, the files
in /usr/lib
are very confusing on MacOS X 10.4. I see...
[Jack-Howarths-Computer:/usr/lib] howarth% cd /usr/lib
[Jack-Howarths-Computer:/usr/lib] howarth% ls -l *gcc*
-rw-r--r-- 1 root wheel 53840 Mar 9 20:17 libgcc_s.1.0.dylib
-rw-r--r-- 1 root wheel 66472 Jun 27 18:46 libgcc_s.1.dylib
-rw-r--r-- 1 root wheel 35188 May 16 12:27 libgcc_s.10.4.dylib
-rw-r--r-- 1 root wheel 35496 May 16 12:27 libgcc_s.10.5.dylib
-rw-r--r-- 1 root wheel 60432 Mar 20 2005 libgcc_s_ppc64.1.0.dylib
-rw-r--r-- 1 root wheel 68972 Jan 30 2006 libgcc_s_ppc64.1.dylib
I see separate libgcc_s.1.0.dylib and libgcc_s.1.dylib as well as
libgcc_s_ppc64.1.0.dylib and libgcc_s_ppc64.1.dylib files (with
different sizes and timestamps) rather than a symlink from one
to the other. This seems to fly in the face of convention (as well
as being at odds with how all the other shared libs in /usr/lib
on Darwin are handled...i.e. with symlinks). Which libgcc should I be
looking for TImode symbols in?
Jack
