From: Andrew Pinski <pinskia@physics.uc.edu>
To: Dara Hazeghi <dhazeghi@yahoo.com>
Cc: gcc@gcc.gnu.org
Subject: Re: cross-compilation documentation
Date: Sun, 22 Jun 2003 17:49:00 -0000 [thread overview]
Message-ID: <BB15CB3A-A4D5-11D7-AD8C-000393A6D2F2@physics.uc.edu> (raw)
In-Reply-To: <20030622171025.90489.qmail@web41110.mail.yahoo.com>
It is documented, just not fully:
"that each --with option has a corresponding --without option"
--with-headers
--with-headers=dir
Deprecated in favor of --with-sysroot. Specifies that target headers
are available when building a cross compiler. The dir argument
specifies a directory which has the target include files. These
include files will be copied into the gcc install directory. This
option with the dir argument is required when building a cross
compiler, if prefix/target/sys-include doesn't pre-exist. If
prefix/target/sys-include does pre-exist, the dir argument may be
omitted. fixincludes will be run on these files to make them
compatible with GCC.
Thanks,
Andrew Pinski
On Sunday, Jun 22, 2003, at 13:10 US/Eastern, Dara Hazeghi wrote:
>> No you do not have install the headers because you
> can pass to gcc
>> --without-headers and that will make sure that you do
> not compile
>> the sources that require glibc's headers.
>
> Where is this documented? I don't see any reference at
> http://gcc.gnu.org/install/configure.html.
>
> Dara
>
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
>
>
next prev parent reply other threads:[~2003-06-22 17:19 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-22 17:43 Dara Hazeghi
2003-06-22 17:49 ` Jan-Benedict Glaw
2003-06-22 17:49 ` Andrew Pinski [this message]
2003-06-22 17:53 ` Jan-Benedict Glaw
2003-06-24 5:26 ` Jim Wilson
2003-06-22 19:36 ` Dara Hazeghi
2003-06-27 12:13 ` Gerald Pfeifer
-- strict thread matches above, loose matches on Subject: below --
2004-05-29 6:25 Dan Kegel
2004-05-29 6:57 ` Zack Weinberg
2004-06-01 16:35 ` Dan Kegel
2004-06-01 17:38 ` Dave Korn
2004-06-01 17:45 ` Peter Barada
2003-06-18 0:36 Dan Kegel
2003-06-18 14:58 ` Joel Sherrill
2003-06-22 17:10 ` Dan Kegel
2003-06-19 0:00 ` Jim Wilson
2003-06-22 17:12 ` Dan Kegel
2003-06-22 17:19 ` Andrew Pinski
2003-06-22 17:21 ` Dan Kegel
2003-06-22 17:35 ` Peter Barada
2003-06-22 17:50 ` Andrew Pinski
2003-06-22 17:56 ` Jan-Benedict Glaw
2003-06-22 18:07 ` Zack Weinberg
2003-06-22 20:15 ` Dan Kegel
2003-06-22 20:27 ` Zack Weinberg
2003-06-22 20:36 ` Peter Barada
2003-06-22 21:10 ` Daniel Jacobowitz
2003-06-23 3:06 ` Dan Kegel
2003-06-23 4:08 ` Jan-Benedict Glaw
2003-06-23 4:22 ` Dan Kegel
2003-06-23 9:10 ` Peter Barada
2003-06-23 12:20 ` Dan Kegel
2003-06-23 12:15 ` Peter Barada
2003-06-23 12:20 ` Dan Kegel
2003-06-23 14:14 ` Peter Barada
2003-06-23 15:38 ` Hans-Peter Nilsson
2003-06-23 16:04 ` Dan Kegel
2003-06-23 16:11 ` Hans-Peter Nilsson
2003-06-23 15:57 ` Dan Kegel
2003-06-23 13:01 ` Daniel Jacobowitz
2003-06-23 14:14 ` Peter Barada
2003-06-23 14:50 ` Daniel Jacobowitz
2003-06-23 14:10 ` Daniel Jacobowitz
2003-06-22 18:41 ` Daniel Jacobowitz
2003-06-22 17:30 ` Jan-Benedict Glaw
2001-11-13 16:21 Cross-compilation documentation Joseph S. Myers
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=BB15CB3A-A4D5-11D7-AD8C-000393A6D2F2@physics.uc.edu \
--to=pinskia@physics.uc.edu \
--cc=dhazeghi@yahoo.com \
--cc=gcc@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).