On Sat, Jun 09, 2007, Ralf S. Engelschall wrote:
> On Sat, Jun 09, 2007, Anders F Björklund wrote:
>
> > > I've now tried to build our "gcc" package (GCC 4.2.0). t starts just
> > > Ifine and compiles lots of things, but then it unfortunately fails
> > > [...]
> >
> > > | strip -o libgcc_s.10.4.dylib_T${mlib} \
> > > | -s
> > > /Users/rse/openpkg/RPM/TMP/gcc-4.2.0/obj/../gcc/config/i386/darwin-libgcc.10.4.ver
> > > -c -u \
> > > | ./${mlib}/libgcc_s.1.dylib.tmp || exit 1 ; \
> > > | done
> > > | strip: can't open file:
> > > /Users/rse/openpkg/RPM/TMP/gcc-4.2.0/obj/gcc/libgcc_s.1.dylib.tmp (No such
> > > file or directory)
> > > | make[3]: *** [libgcc_s.10.4.dylib] Error 1
> > > | make[2]: *** [all-stage1-gcc] Error 2
> > > | make[1]: *** [stage1-bubble] Error 2
> > > | make: *** [bootstrap-lean] Error 2
> > >
> > > Has anybody already seen this problem related to libgcc_s.1.dylib?
> >
> > Yes, it's a known problem - Darwin doesn't support static libgcc:
> >
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26510
> >
> > > Was anybody already successful in building a stock GCC 4.2.0 under Mac OS
> > > X?
> >
> > My computer unfortunately started kernel panicking recently,
> > so I will have to downgrade to Mac OS X 10.4.8 and try again...
> >
> > I think it should work without the --disable-shared, though ?
>
> Ok, let's see: I'll retry with --enable-shared...
Hmmm... now the library was built but a tool (I've never heard of in my
Unix life) named "lipo" now complains:
| # When building multilibbed target libraries, all the required
| # libraries are expected to exist in the multilib directory.
| MLIBS=`/Users/rse/openpkg/RPM/TMP/gcc-4.2.0/obj/./gcc/xgcc
-B/Users/rse/openpkg/RPM/TMP/gcc-4.2.0/obj/./gcc/
-B/Users/rse/openpkg/i386-apple-darwin8.9.1/bin/
-B/Users/rse/openpkg/i386-apple-darwin8.9.1/lib/ -isystem
/Users/rse/openpkg/i386-apple-darwin8.9.1/include -isystem
/Users/rse/openpkg/i386-apple-darwin8.9.1/sys-include --print-multi-lib \
| | sed -e 's/;.*$//' -e '/^\.$/d'` ; \
| for mlib in $MLIBS ; do \
| rm -f ${mlib}/libgcc_s.10.4.dylib || exit 1 ; \
| ln -s ../libgcc_s.10.4.dylib ${mlib}/libgcc_s.10.4.dylib || exit 1
; \
| done
| MLIBS=`/Users/rse/openpkg/RPM/TMP/gcc-4.2.0/obj/./gcc/xgcc
-B/Users/rse/openpkg/RPM/TMP/gcc-4.2.0/obj/./gcc/
-B/Users/rse/openpkg/i386-apple-darwin8.9.1/bin/
-B/Users/rse/openpkg/i386-apple-darwin8.9.1/lib/ -isystem
/Users/rse/openpkg/i386-apple-darwin8.9.1/include -isystem
/Users/rse/openpkg/i386-apple-darwin8.9.1/sys-include --print-multi-lib \
| | sed -e 's/;.*$//' -e '/^\.$/d'` ; \
| for mlib in '' $MLIBS ; do \
| strip -o libgcc_s.10.4.dylib_T${mlib} \
| -s
/Users/rse/openpkg/RPM/TMP/gcc-4.2.0/obj/../gcc/config/i386/darwin-libgcc.10.4.ver
-c -u \
| ./${mlib}/libgcc_s.1.dylib.tmp || exit 1 ; \
| done
| lipo -output libgcc_s.10.4.dylib -create libgcc_s.10.4.dylib_T*
| lipo: can't figure out the architecture type of: libgcc_s.10.4.dylib_T
| make[3]: *** [libgcc_s.10.4.dylib] Error 1
| make[2]: *** [all-stage1-gcc] Error 2
| make[1]: *** [stage1-bubble] Error 2
| make: *** [bootstrap-lean] Error 2
| error: Bad exit status from /Users/rse/openpkg/RPM/TMP/rpm-tmp.9343 (%build)
Seems like "lipo" is some sort of a tool for the Universal Binaries
stuff of Mac OS X and the generated libgcc_s.10.4.dylib file seems to be
not carrying the information it expects. Hmmm.. but for the generation
of this file now the Mac OS X tool chain is used. Why to the hell is
this Mac OS X platform such "different" and is not willing to just play
nicely with us!?
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
OpenPKG http://openpkg.org
Developer Communication List openpkg-dev@openpkg.org
