Re: Unreviewed patch / {PATCH] Do not override configure decision about inhibit_libc

[Joern Rennecke <joern.rennecke@superh.com>]

Momchil Velikov wrote:
> 
> >>>>> "Joern" == Joern Rennecke <joern.rennecke@superh.com> writes:
> 
> Joern> Momchil Velikov wrote:
> >>
> >> >>>>> "Joern" == Joern Rennecke <joern.rennecke@superh.com> writes:
> Joern> How do you build a usable sh-elf compiler without newlib
> Joern> in the first place?
> >>
> >> Huh ? The compiler by itself does not require newlib nor does the
> >> produced code, right ?
> 
> Joern> It you need header files for the compiler if you compile code
> Joern> that include any of them.  And you need the c library if any
> Joern> function of it is used.
> 
> I can think of at least three legitimate cases:
> 
> I. Use the compiler in a freestanding environment - no libraies or
> headers exist at all.

Is there a demand for this configuration?  In that case, we should
have something more fine-grained that inhibit_libc, which suppresses
the profiling support along with eprintf.
	
> II. Build and install the libraries after building the compiler - way
> more convenient than installing headers only, building the compiler,
> going back and building the libraries.

It's also more convenient that writing all the binaries by hand.  But
still moe convenient is just to use a unified source tree and build
everything in one go.
> 
> III. In a cross compilation environment, the headers may not be on the
> same machine.

Why would you want to build the libraries on a different machine than
the compiler?
	
-- 
--------------------------
SuperH
2430 Aztec West / Almondsbury / BRISTOL / BS32 4AQ
T:+44 1454 462330