[Bug bootstrap/28962] building a cross compiler with --disable-multilib fails

2008-12-28 Thread pinskia at gcc dot gnu dot org
--- Comment #9 from pinskia at gcc dot gnu dot org 2008-12-28 21:28 --- You should disable libmudflap and libssp (in newer gcc's) if you want to build a cross compiler to start stage1. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added

[Bug bootstrap/28962] building a cross compiler with --disable-multilib fails

2006-09-12 Thread pinskia at gcc dot gnu dot org
--- Comment #8 from pinskia at gcc dot gnu dot org 2006-09-13 06:23 --- (In reply to comment #7) > Is there a good reason why gcc can't officially support being built without a > libc by either figuring out that there's no libc itself or by offering some > kind of --i-do-not-have-a-libc

[Bug bootstrap/28962] building a cross compiler with --disable-multilib fails

2006-09-06 Thread bunk at stusta dot de
--- Comment #7 from bunk at stusta dot de 2006-09-06 17:22 --- I don't have a glibc for this target. But this might be where my problems are coming from: I am able to compile gcc 4.1.1 for at about a dozen targets without having any libc for these targets present. And the resulting com

[Bug bootstrap/28962] building a cross compiler with --disable-multilib fails

2006-09-06 Thread pinskia at gcc dot gnu dot org
--- Comment #6 from pinskia at gcc dot gnu dot org 2006-09-06 16:32 --- /usr/local/DIR/gcc-powerpc64-svn20060906/powerpc64-linux/sys-include -O2 -g -O2 conftest.c >&5 /usr/local/bin/powerpc64-linux-ld: crt1.o: No such file: No such file or directory collect2: ld returned 1 exit statu