This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: 2.95,2 bug; can not create cross compiler


At 20:44 18.11.99 , Mike Stump wrote:
> > Date: Thu, 18 Nov 1999 16:40:36 GMT
> > To: mrs@windriver.com
> > From: jlarmour@cygnus.co.uk (Jonathan Larmour)
>
> > Isn't this what --without-newlib is for?
>
>I don't understand the relevance of the question.  No is the only
>answer I can imagine.  Or put another way, I am not using newlib, and
>I don't want to inhibit_libc as I have one.  I don't want to lie to
>the compiler and claim I have newlib, and currently, --without-newlib
>is how it my tree is configured and that is the default for me.

He probably means --with-newlib and is referring to the original problem. 
If you just want a naked crosscompiler with no target libraries or headers 
around (and no newlib), this will define you inhibit_libc (see 
gcc/configure). --with-newlib probably should be duplicated with a more 
sensible name like --no-target-stuff :-).

Franz.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]