This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I just ran into the problem you describe. I have been updating Bill Gatliff's scripts to support newer toolchains. Yesterday I tried glibc-2.3.2 (had been using glibc-2.2.5). To my horror, it refused to configure without having a cross gcc. Since you have to configure and install-headers for glibc before you can compile the cross gcc, this is indeed a catch-22. I suspect we can fool the configure by the following ruse:
# glibc-2.3.x requires a cross-compiler even here, so shoot it in the head # FIXME need to file a bug report against glibc for this mkdir fake-cross ln -s `which gcc` fake-cross/${TARGET}-gcc PATH=`pwd`/fake-cross:$PATH ...
I verified this gets us past configure, but haven't finished a build yet. Knock on wood.
I've got my sledgehammer out and I'm pounding on trees :-)
I think you could also get around this by setting CC rather than playing games with fake cross compilers and PATH, but I haven't checked.
For completeness, here's the error message associated with the bug: configure: error: *** These critical programs are missing or too old: gcc *** Check the INSTALL file for required versions.
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |