[Bug c/40353] New: [GCC-4.4.0] configure --with-sysroot needs header files, but it should not

[Bug c/40353] New: [GCC-4.4.0] configure --with-sysroot needs header files, but it should not

[no dot spam dot to dot me at ish dot de]

Hello!

I try to build a cross compiler with sysroot support- before I build one
without sysroot support.

To build without sysroot support I used the following configure options:

--prefix="${CROSS_DIR}" --target="${BUILD_TARGET}" --with-cpu=405 --disable-nls
--disable-shared --disable-multilib --disable-decimal-float --disable-threads
--disable-libmudflap --disable-libssp --disable-libgomp --enable-languages=c

It compiled without having a libc installed (just binutils, of course).

Now I want to build a cross compiler with sysroot- support (binutils compiled
fine) with the following options:

--prefix="${CROSS_DIR}" --target="${BUILD_TARGET}"
--with-sysroot="${CROSS_DIR}" --with-cpu=405 --disable-nls --disable-shared
--disable-multilib --disable-decimal-float --disable-threads
--disable-libmudflap --disable-libssp --disable-libgomp --enable-languages=c

Now libc- headers are needed. Even when --without-headers is given as option.
I don't understand that.


-- 
           Summary: [GCC-4.4.0] configure --with-sysroot needs header files,
                    but it should not
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: no dot spam dot to dot me at ish dot de
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: powerpc-405-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40353

[Bug other/40353] [GCC-4.4.0] configure --with-sysroot needs header files, but it should not

[jsm28 at gcc dot gnu dot org]

------- Comment #1 from jsm28 at gcc dot gnu dot org  2009-11-22 19:52 -------
The magic option to allow system headers not to be present (for an early
compiler in a series of multiple compiler/libc builds / header installs
to bootstrap a full toolchain) is --with-newlib, but this should be
documented (and preferably there should be a more meaningful option
to enable inhibit_libc directly).


-- 

jsm28 at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
          Component|c                           |other
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2009-11-22 19:52:20
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40353