Thanks a lot! I ask my users to install the optional 32-bit libs. Oliver On Sun, Nov 30, 2008 at 11:51:44PM +0200, Kai Ruottu wrote: > Oliver Kullmann wrote: > > >What can I do to build gcc 4.1.2 on machines where > >that error message > > > >In file included from /usr/include/features.h:354, > > from /usr/include/stdio.h:28, > > from > > /compsci/saturn/staff/csoliver/OKplatform/ExternalSources/builds/Gcc/gcc-4.1.2/gcc/tsystem.h:90, > > from > > /compsci/saturn/staff/csoliver/OKplatform/ExternalSources/builds/Gcc/gcc-4.1.2/gcc/crtstuff.c:68: > >/usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or > >directory > >make[5]: *** [32/crtbegin.o] Error 1 > > > >shows up (when building gcc)?? > > > >One guess is that the "glibc-devel i386" (or "glibc 32 bit") libraries > >need to be installed? > > Yes, that is the problem! The Linux/x86_64 target GCC is bi-arch and > supports both 64-bit and 32-bit development so there should be both > 64-bit (default) and 32-bit (optional) libraries installed before one > could try to built a new GCC... (with the build defaults) > > >(My problem is that I don't have access to these machines --- but if I can > >tell the users > >to do something, and it cures the problem, then we all are happy.) > > They should simply install the optional 32-bit libs... Or if the 32- > bit support is never needed/used, using the '--disable-multilib' in > GCC configure might disable building the 32-bit parts.... > > If the target distro is known, SuSE/x86_64, Fedora/x86_64, CentOS/x86_64 > or what? And one has no access to the target machine, then maybe its > glibcs however are freely available... So producing a crosstoolchain for > it is still possible. Stuff for Open SuSE, Fedora, Ubuntu, CentOS etc is > freely downloadable but stuff for RHEL etc Linuces isn't :(
