To reactivate this old 486 laptop that's been sitting in my basement, I set out to install it with a tiny Gentoo system and use it as a DSL router. The HD is 1.3 GB, so a full glibc-based system wouldn't be much of a problem, but I wanted to experiment with embedded stuff anyway, so... Well, I've never sone a Stage1 install. Upon my first try with Gentoo I ran into some problem and thought WTH, I'll just go with Stage3. But now, following the HOWTO at http://www.bulah.com/embeddedgentoo.html, I have to do it. All is fine up to the bootstrapping. I have a P4 Gentoo machine, trying to compile for i486. My short make.conf:
CFLAGS="-Os -march=i486 -pipe -fomit-frame-pointer"
CHOST="i486-gentoo-linux-uclibc"
CXXFLAGS="${CFLAGS}"
FEATURES="-sandbox buildpkg"
UCLIBC_CPU="486"
USE="bitmap-fonts minimal truetype-fonts"
Trying to boostrap gcc fails with a segfault:
gengtype-yacc.c: In function `yydestruct':
gengtype-yacc.c:725: warning: traditional C rejects ISO C style function
definitions
stage1/xgcc -Bstage1/ -B/usr/i486-gentoo-linux-uclibc/bin/ -DEFAULT_PIE_SSP
-DEFAULT_RELRO -DEFAULT_BIND_NOW -DUSE_UCLIBC -march=i486 -pipe -O2 -DIN_GCC
-W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
-Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERATOR_FILE -o
gengtype \ gengtype.o gengtype-lex.o gengtype-yacc.o ../libiberty/libiberty.a
/usr/i486-gentoo-linux-uclibc/bin/ld: warning: creating a DT_TEXTREL in object.
./gengtype
make[2]: *** [s-gtype] Segmentation fault
make[2]: Leaving directory
`/var/tmp/portage/gcc-3.3.5.20050130-r1/work/build/gcc'
make[1]: *** [stage2_build] Error 2
make[1]: Leaving directory
`/var/tmp/portage/gcc-3.3.5.20050130-r1/work/build/gcc'
make: *** [bootstrap-lean] Error 2
I found that if I hack the Makefile to link all of those helper programs
in gcc-3.3.5.20050130-r1/work/build/gcc statically, they won't segfault
and even produce something that will compile. But then I get another
segfault when the resulting "xgcc" binary is run for the first time, so
there is probably a systematic problem.
Any ideas on what might be going wrong would be highly appreciated.
cheers!
Matthias
--
I prefer encrypted and signed messages. KeyID: 90CF8389
Fingerprint: 8E 1F 10 81 A4 66 29 46 B9 8A B9 E2 09 9F 3B 91
pgp3RJky1kgw1.pgp
Description: PGP signature
