JérÎme Carretero <[EMAIL PROTECTED]> writes: > > For some time I've been wanting to build a cross-compilation toolchain to use distcc on my machines having > different architectures, but contrarius didn't like me much. > Tonight, exceeded, I decided to succeed in using it. > > The first machines : the i686 one is MacGyver and the x86_64 one is newnew. > > In the next paragraph I'm telling my installation story on MacGyver, hoping to help (could be useful to > #paludis troubleshooters, or users grepping the ML). > As contrarius didn't work out of the box (see ticket #552) I have had to use "-* nocxx" use flags for > cross-(i686|x86_64)-pc-linux-gnu/gcc (version 4.2.3 FYI). > > Then, wanting to compile C++ stuff, I tried to install gcc with C++ support. > For that, you need glibc (if you try to build gcc without nocxx, gcc build miserably fails, complaining > about glibc missing headers (in config.log, the displayed reason is something not useful)). >
thanks much for this information. I am trying to get cross compiling working for cross-i686-pc-linux-gnu with gcc 4.3.1-r1. Breaking during the minimal gcc stage with /var/tmp/paludis/cross-i686-pc-linux-gnu-gcc-4.3.1-r1/work/gcc-4.3.1/libgcc /config/libbid/bid_decimal_globals.c:52:18: error: fenv.h: No such file or directory ... I tried setting keywords to 'cross-i686-pc-linux-gnu/gcc -* nocxx' or 'cross-i686-pc-linux-gnu/gcc -* nocxx build' and '*/* crosscompile_opts: headers-only'. Also tried the latest version of binutils. No luck with any of that. Here are some clues to what is going on: http://bugs.gentoo.org/show_bug.cgi?id=227065 http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys- devel/crossdev/files/crossdev?r1=1.103&r2=1.104 But I am not sure what is going wrong here. _______________________________________________ paludis-user mailing list [email protected] http://lists.pioto.org/mailman/listinfo/paludis-user
