* Arnd Bergmann <arnd@bergmann-dalldorf.de> [030122 16:55]: > Cool. Can you post the .config you used for your kernel? That would be great. > > BTW, I found that the gcc build gave me endless problems unless I > > passed --disable-multilib to configure. Also, it wants to link > > libgcc_s.so against -lc, while glibc wants to link against libgcc.a, > > so you won't be able to compile either all the way through the first > > time. > I solved this by installing the glibc rpm package from ftp.suse.com > and bootstrapping gcc from there. The gcc and glibc packages on my > page are now independent from that and only need each other (and > biarch binutils). I had to make some changes to gcc files to allow > making 32 bit output the default. Appearantly all the others so > far have gcc installed as a native x86_64 compiler with an extra > 32 bit mode. The steps on the x86-64.org website specifically avoid this problem by generating the libgcc in a first pass, and then building hte full compiler: http://www.x86-64.org/documentation_folder/build Note that when building gcc the first time you set: --enable-languages=c --disable-shared \ --disable-multilib --enable-threads=single Which just generates a dumb compiler, but one that is self bootstrapped. B. -- WebSig: http://www.jukie.net/~bart/sig/
Attachment:
pgpYjkAVaVJtI.pgp
Description: PGP signature