From: Richard Zidlicky <Richard.Zidlicky@stud.informatik.uni-erlangen.de>
To: Joern Rennecke <joern.rennecke@superh.com>
Cc: Momchil Velikov <velco@fadata.bg>,
gcc@gcc.gnu.org, dje@transmeta.com,
Zack Weinberg <zack@codesourcery.com>
Subject: Re: Unreviewed patch / {PATCH] Do not override configure decision about inhibit_libc
Date: Sun, 28 Jul 2002 22:31:00 -0000 [thread overview]
Message-ID: <20020727215310.A769@linux-m68k.org> (raw)
In-Reply-To: <3D3FF1EC.39BA039A@superh.com>; from joern.rennecke@superh.com on Thu, Jul 25, 2002 at 01:41:16PM +0100
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
prev parent reply other threads:[~2002-07-28 8:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 7:34 Unreviewed patch Momchil Velikov
2002-07-25 9:24 ` Unreviewed patch / {PATCH] Do not override configure decision about inhibit_libc Joern Rennecke
2002-07-25 9:46 ` Momchil Velikov
2002-07-25 9:51 ` Joern Rennecke
2002-07-25 10:01 ` Momchil Velikov
2002-07-25 11:01 ` Joern Rennecke
2002-07-25 11:22 ` Momchil Velikov
2002-07-25 23:23 ` Joern Rennecke
2002-07-28 22:31 ` Richard Zidlicky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020727215310.A769@linux-m68k.org \
--to=richard.zidlicky@stud.informatik.uni-erlangen.de \
--cc=dje@transmeta.com \
--cc=gcc@gcc.gnu.org \
--cc=joern.rennecke@superh.com \
--cc=velco@fadata.bg \
--cc=zack@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).