Alexander,
Apple has always built libgcc in that manner. It is the one exception
in the multilib build where a separate subdirectory isn't used. The
new versioned libgcc_ext stubs (which provide all the additional symbols
from FSF libgcc which aren't in libgcc_s.10.4/10.5) is built the same way.
This is because libgcc_ext builds with the same infrastructure.
Jack
On Wed, Aug 25, 2010 at 08:58:10PM -0400, Alexander Hansen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I'm not sure if this is intentional, but I get the following from
> gcc44-4.4.4-1000 (similarly for gcc45-4.5.0-1000) on 10.6/i386 and 10.5/i386
>
> $ dpkg -L gcc44-shlibs | grep dylib | xargs file
> /sw32/lib/gcc4.4/lib/gcj-4.4.4-10/libjvm.dylib: Mach-O
> dynamically linked shared library i386
> /sw32/lib/gcc4.4/lib/libffi.4.dylib: Mach-O
> dynamically linked shared library i386
> /sw32/lib/gcc4.4/lib/libgcc_s.1.dylib: Mach-O universal
> binary with 2 architectures
> /sw32/lib/gcc4.4/lib/libgcc_s.1.dylib (for architecture i386): Mach-O
> dynamically linked shared library i386
> /sw32/lib/gcc4.4/lib/libgcc_s.1.dylib (for architecture x86_64): Mach-O
> 64-bit dynamically linked shared library x86_64
> /sw32/lib/gcc4.4/lib/libgcc_s.10.4.dylib: Mach-O universal
> binary with 2 architectures
> /sw32/lib/gcc4.4/lib/libgcc_s.10.4.dylib (for architecture i386): Mach-O
> dynamically linked shared library stub i386
> /sw32/lib/gcc4.4/lib/libgcc_s.10.4.dylib (for architecture x86_64):
> Mach-O 64-bit dynamically linked shared library stub x86_64
> /sw32/lib/gcc4.4/lib/libgcc_s.10.5.dylib: Mach-O universal
> binary with 2 architectures
> /sw32/lib/gcc4.4/lib/libgcc_s.10.5.dylib (for architecture i386): Mach-O
> dynamically linked shared library stub i386
> /sw32/lib/gcc4.4/lib/libgcc_s.10.5.dylib (for architecture x86_64):
> Mach-O 64-bit dynamically linked shared library stub x86_64
> /sw32/lib/gcc4.4/lib/libgcj-tools.10.dylib: Mach-O
> dynamically linked shared library i386
> /sw32/lib/gcc4.4/lib/libgcj.10.dylib: Mach-O
> dynamically linked shared library i386
> /sw32/lib/gcc4.4/lib/libgfortran.3.dylib: Mach-O
> dynamically linked shared library i386
> /sw32/lib/gcc4.4/lib/libgij.10.dylib: Mach-O
> dynamically linked shared library i386
> /sw32/lib/gcc4.4/lib/libgomp.1.dylib: Mach-O
> dynamically linked shared library i386
> /sw32/lib/gcc4.4/lib/libobjc-gnu.2.dylib: Mach-O
> dynamically linked shared library i386
> /sw32/lib/gcc4.4/lib/libssp.0.dylib: Mach-O
> dynamically linked shared library i386
> /sw32/lib/gcc4.4/lib/libstdc++.6.dylib: Mach-O
> dynamically linked shared library i386
> /sw32/lib/gcc4.4/lib/x86_64/gcj-4.4.4-10/libjvm.dylib: Mach-O 64-bit
> dynamically linked shared library x86_64
> /sw32/lib/gcc4.4/lib/x86_64/libffi.4.dylib: Mach-O 64-bit
> dynamically linked shared library x86_64
> /sw32/lib/gcc4.4/lib/x86_64/libgcj-tools.10.dylib: Mach-O 64-bit
> dynamically linked shared library x86_64
> /sw32/lib/gcc4.4/lib/x86_64/libgcj.10.dylib: Mach-O 64-bit
> dynamically linked shared library x86_64
> /sw32/lib/gcc4.4/lib/x86_64/libgfortran.3.dylib: Mach-O 64-bit
> dynamically linked shared library x86_64
> /sw32/lib/gcc4.4/lib/x86_64/libgij.10.dylib: Mach-O 64-bit
> dynamically linked shared library x86_64
> /sw32/lib/gcc4.4/lib/x86_64/libgomp.1.dylib: Mach-O 64-bit
> dynamically linked shared library x86_64
> /sw32/lib/gcc4.4/lib/x86_64/libobjc-gnu.2.dylib: Mach-O 64-bit
> dynamically linked shared library x86_64
> /sw32/lib/gcc4.4/lib/x86_64/libssp.0.dylib: Mach-O 64-bit
> dynamically linked shared library x86_64
> /sw32/lib/gcc4.4/lib/x86_64/libstdc++.6.dylib: Mach-O 64-bit
> dynamically linked shared library x86_64
>
> The 64-bit libs aren't a problem, but the universal ones seem like
> they'd cause issues down the road.
> - --
> Alexander Hansen
> Fink User Liaison
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEUEARECAAYFAkx1vCIACgkQB8UpO3rKjQ+b+gCghnGlt/Z4wpQb6qQ+Jtelr6gK
> FXUAkgP786OccF9aSGqKyHRZmfIQLAI=
> =PCSD
> -----END PGP SIGNATURE-----
------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
