|Summary:||crossdev for m68k-linux target failed|
|Product:||Gentoo Linux||Reporter:||James Le Cuirot <chewi>|
|Component:||[OLD] Core system||Assignee:||Gentoo Toolchain Maintainers <toolchain>|
|Package list:||Runtime testing required:||---|
Description James Le Cuirot 2006-02-20 14:11:18 UTC
I'm trying to use crossdev to build the complete toolchain for m68k. I have successfully done this once before but it doesn't seem to work anymore. When compiling gcc (3.4.4 or 3.4.5) for stage 1, it bombs out, starting with this. In file included from ./gthr-default.h:1, from /var/tmp/cross/m68k-linux/portage/gcc-3.4.5/work/gcc-3.4.5/gcc/gthr.h:96, from /var/tmp/cross/m68k-linux/portage/gcc-3.4.5/work/gcc-3.4.5/gcc/unwind-dw2-fde-glibc.c:50: /var/tmp/cross/m68k-linux/portage/gcc-3.4.5/work/gcc-3.4.5/gcc/gthr-posix.h:43:21: pthread.h: No such file or directory /var/tmp/cross/m68k-linux/portage/gcc-3.4.5/work/gcc-3.4.5/gcc/gthr-posix.h:44:20: unistd.h: No such file or directory This problem is widely mentioned on Google. It happens because it's asking for kernel headers when glibc hasn't been compiled yet. Most people suggest using --disable-threads to compile gcc the first time. Is this absolutely necessary and can this be resolved for crossdev? I don't really understand why this is only happening now when I managed to successfully cross-compile gcc 3.4.4 a while back.
Comment 1 SpanKY 2006-02-20 14:23:58 UTC
we patch gcc stage1 so it doesnt require headers you didnt post any of the logs that crossdev told you to, nor did you post `emerge info` like you were supposed to
Comment 2 James Le Cuirot 2006-02-20 14:30:34 UTC
Created attachment 80317 [details] cross-m68k-linux-gcc-stage1.log
Comment 3 James Le Cuirot 2006-02-20 14:30:57 UTC
Created attachment 80318 [details] cross-m68k-linux-info.log
Comment 4 James Le Cuirot 2006-02-20 14:32:05 UTC
Sorry. I thought that would be enough info for you to go on.
Comment 5 James Le Cuirot 2006-02-26 03:54:01 UTC
If it helps at all, I managed to compile a native version of gcc 3.4.5 for m68k-linux without any problems.
Comment 6 SpanKY 2006-04-09 21:30:03 UTC
ok, the problem is your target use m68k-linux-gnu