Hi Joeseph,
On 9 November 2011 11:39, Joseph S. Myers <jos...@codesourcery.com> wrote: > On Wed, 9 Nov 2011, Linas Vepstas wrote: > >> I've run into a bootstrapping issue which I'd like to solve >> "the right way", instead of continuing to hack around it. >> >> Briefly: I can't build glibc without libgcc_eh.a, which is >> provided by gcc. However, libgcc_eh.a is not built, unless >> I configure gcc with --enable-shared. But doing so causes >> gcc to attempt to build libgcc_s.so, which fails because it >> wants to link to libc.so, which hasn't been built yet. And >> so it goes.... > > The usual approach involves building three compilers and configuring glibc > twice. > > http://www.eglibc.org/cgi-bin/viewvc.cgi/trunk/libc/EGLIBC.cross-building?revision=2037 > > NB this involves EGLIBC features not in FSF glibc to make bootstrapping > easier. For FSF glibc you may need to use a config.cache with > > libc_cv_forced_unwind=yes > libc_cv_c_cleanup=yes > > in it (both times you configure glibc), for the initial headers > installation install bits/stdio_lim.h manually and also create gnu/stubs.h > manually. I'll try that. Currently, even an infinite number of gcc/glibc rebuilds didn't get me out of this bootstrapping loop, and yes, I was building against FSF not eglibc. I know that the current FSF policy is to support only the major arches, but I'd like to see the FSF code fix up bootstrapping issues like this. --linas
