This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/28962] building a cross compiler with --disable-multilib fails
- From: "bunk at stusta dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 Sep 2006 17:22:41 -0000
- Subject: [Bug bootstrap/28962] building a cross compiler with --disable-multilib fails
- References: <bug-28962-9876@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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 compilers work fine for my
purposes (cross-compiling Linux kernels).
But the configure options I had to figure out for doing this seem to indicate
that this is a working but not documented setup.
It seems sending a bug report for part of this wasn't the right solution.
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 option to configure?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28962