From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: rbmj <rbmj@verizon.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Fixincludes permanence & questions on cross compilers
Date: Wed, 23 May 2012 17:27:00 -0000 [thread overview]
Message-ID: <CAH6eHdQ1Rw92ms--6rfHY6mY-kyD6Kdc1AXjrOW8_ECNhgdnZQ@mail.gmail.com> (raw)
In-Reply-To: <4FBD15EB.6090105@verizon.net>
On 23 May 2012 17:52, rbmj wrote:
> Hi all,
>
> Two questions:
>
> 1. Are fixincludes hacks only active during build-time (e.g. they do not
> replace the actual file) or are they permanent? If they are only
> temporary/local to gcc, but they need to be permanent, is there a way to
> specify this?
They are permanent, but they don't replace the file. GCC puts the
fixed headers in a directory which it searches before the system
directories, so it finds the fixed ones before the original ones.
> 2. On cross compilers, fixincludes does not appear (to my uneducated eye)
> to be applied to my headers (then again, I may have written the hacks wrong)
> located in sys-include. Does fixincludes not affect headers in sys-include
> or am I not looking hard enough?
If you're expecting the original headers to be replaced then you're
looking in the wrong place.
Search under the GCC installation tree, you should find the fixed
version of the header.
next prev parent reply other threads:[~2012-05-23 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 16:53 rbmj
2012-05-23 17:27 ` Jonathan Wakely [this message]
2012-05-23 18:04 ` rbmj
2012-05-25 12:08 ` Why is fixincludes not doing anything? (was: Re: Fixincludes permanence & questions on cross compilers) rbmj
2012-05-25 14:00 ` Ian Lance Taylor
2012-05-25 14:24 ` Why is fixincludes not doing anything? rbmj
2012-05-25 23:19 ` Ian Lance Taylor
2012-05-26 19:58 ` rbmj
[not found] ` <4FC128C8.1060604@verizon.net>
[not found] ` <mcrr4u6iufn.fsf@dhcp-172-18-216-180.mtv.corp.google.com>
2012-05-26 20:54 ` rbmj
2012-05-27 6:08 ` rbmj
2012-05-29 19:13 ` rbmj
2012-05-29 22:48 ` Ian Lance Taylor
2012-06-01 17:32 ` rbmj
2012-06-01 19:44 ` Ian Lance Taylor
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=CAH6eHdQ1Rw92ms--6rfHY6mY-kyD6Kdc1AXjrOW8_ECNhgdnZQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=rbmj@verizon.net \
/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).