From: Ian Lance Taylor <iant@google.com>
To: booleandomain <booleandomain@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: --without-headers and --with-newlib configure options
Date: Thu, 23 Jul 2009 17:26:00 -0000 [thread overview]
Message-ID: <m3vdlj5n1k.fsf@google.com> (raw)
In-Reply-To: <h4a1a5$qc$1@ger.gmane.org> (booleandomain@gmail.com's message of "Thu\, 23 Jul 2009 17\:59\:21 -0700")
booleandomain <booleandomain@gmail.com> writes:
> I have some doubts about the --without-headers and --with-newlib
> options when configuring a cross-compiler.
>
> The only source of informations about these options I'm aware of is
> http://gcc.gnu.org/install/configure.html. There it is written:
>
> --without-headers: Tells GCC not use any target headers from a libc
> when building a cross compiler.
> --with-newlib: Specifies that `newlib' is being used as the target C
> library.
>
> In other words --without-headers means not to use any libc headers,
> while --with-newlib means to use newlib headers. So in my opinion
> --without-headers --with-newlib doesn't make any sense. Despite of
> this, I have often seen in the web both options used at the same
> time. Why?
Normally if you use --with-newlib the compiler will build the gcc
support library, libgcc, without requiring any external support from the
C library. Using --without-headers will disable that, and the gcc
support library will be built without requiring any library support.
This disables a few features which are generally uninteresting for
embedded systems.
--with-newlib is still useful even when using --without-headers, because
the newlib header files will be used for libraries other than libgcc,
such as libstdc++.
Ian
next prev parent reply other threads:[~2009-07-23 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 15:58 booleandomain
2009-07-23 17:26 ` Ian Lance Taylor [this message]
2009-07-23 17:48 ` booleandomain
2009-07-23 18:46 ` Ian Lance Taylor
2009-07-23 19:03 ` booleandomain
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=m3vdlj5n1k.fsf@google.com \
--to=iant@google.com \
--cc=booleandomain@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/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).