[Bug bootstrap/8180] --without-headers configure option not working
pgarrone at linuxmail dot org
gcc-bugzilla@gcc.gnu.org
Fri Aug 22 07:36:00 GMT 2003
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8180
------- Additional Comments From pgarrone at linuxmail dot org 2003-08-22 07:35 -------
Subject: Re: --without-headers configure option not
working
Hi,
Sorry about my laxity here
Unfortunatly I am still mired with gcc-3.2.2 and I dont have time just now to set up the latest toolchain, since
I have to complete other aspects of my project. I plan to get back to this in a fortnight or so.
I lieu of doing anything useful like checking your patch, I will give my two cents worth here.
To set up a cross-compiler, it is necessary to first create a compiler without a library (phase 1), then compile a library,
then create the final compiler (phase 2).
At the moment, for phase 1, I have the configure option --without-headers, and for phase 2, --with-libs=... and --with-headers=...
You are suggesting that for newer versions of the compiler, it should be --with-newlib for phase 1,
event though I am not using newlib?
I will most definitly not do that, I like my config files to look sensible, and I will continue to apply my patch thanks.
I suppose that it has to be possible somehow to set inhibit_libc.
If --without-headers is set, then this implies inhibit_libc at the moment.
The whole logic seems a little torturous.
Maybe inhibit_libc should only be set if --without-libs or --with-newlib is a configure option.
That way, for pass 1 for a cross-toolchain, one provides configure options --without-headers and --without-libs.
Then for pass 2, one provides --with-headers=wherever and --with-libs=wherever
Dont consider newlib, except that --with-newlib could mean --with-libs=wherever_newlib_usually_is
I think it is really necessary to keep all this configuration sensible.
----- Original Message -----
From: "dank at kegel dot com" <gcc-bugzilla@gcc.gnu.org>
Date: 21 Aug 2003 12:53:10 -0000
To: pgarrone@linuxmail.org
Subject: [Bug bootstrap/8180] --without-headers configure option not working
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8180
------- Additional Comments From dank at kegel dot com 2003-08-21 12:53 -------
By the way, the workaround in gcc-3.2/gcc-3.3 is to give the --with-newlib
option when configuring gcc, even if you plan to use glibc later.
Sorry I didn't mention that before.
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
More information about the Gcc-bugs
mailing list