This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Unreviewed patch / {PATCH] Do not override configure decision about inhibit_libc
- From: Richard Zidlicky <Richard dot Zidlicky at stud dot informatik dot uni-erlangen dot de>
- To: Joern Rennecke <joern dot rennecke at superh dot com>
- Cc: Momchil Velikov <velco at fadata dot bg>, gcc at gcc dot gnu dot org, dje at transmeta dot com, Zack Weinberg <zack at codesourcery dot com>
- Date: Sat, 27 Jul 2002 21:53:10 +0200
- Subject: Re: Unreviewed patch / {PATCH] Do not override configure decision about inhibit_libc
- References: <3D3FF1EC.39BA039A@superh.com>
On Thu, Jul 25, 2002 at 01:41:16PM +0100, Joern Rennecke wrote:
> 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?
yes. Keeping everything in sync is lot of pain, right now I came
across a problem where distcc fails with '-g' option because the
remote compiler was configured for different binutils..
Richard