From: Jim Wilson <jimw@sifive.com>
To: William Tambe <tambewilliam@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: How to customize GCC builtin search paths
Date: Mon, 13 Apr 2020 13:44:55 -0700 [thread overview]
Message-ID: <CAFyWVab7XmS6AUjdAoYzTvSbpuPx-C9W8qcAhUY1SHBD2Zf1rQ@mail.gmail.com> (raw)
In-Reply-To: <CAF8i9mNpK_7iWndtGTxk_-9L61=2rB_Yvv37fi9Ph9vXC0QXiQ@mail.gmail.com>
On Sun, Apr 12, 2020 at 9:06 AM William Tambe <tambewilliam@gmail.com> wrote:
> I can hardly find examples on how to use startfile_prefixes. Currently
> when running gcc as follow:
> arch-elf-gcc -v test.c
>
> I get the following excerpt showing how gcc looks for includes:
You have the source code. You can find a lot of info by using grep to
search for obvious things, like /usr/include for instance, and then
follow the code to see where it takes you.
But include files are handled differently than startfiles. This is a
different question than the previous one. See cppdefault.c. It isn't
a good idea to try to change this. Stuff will break. See also
include_prefixes in gcc.c.
Jim
next prev parent reply other threads:[~2020-04-13 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 2:52 William Tambe
2020-04-10 17:15 ` Jim Wilson
2020-04-12 16:06 ` William Tambe
2020-04-13 20:44 ` Jim Wilson [this message]
2020-04-13 20:56 ` Jonathan Wakely
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=CAFyWVab7XmS6AUjdAoYzTvSbpuPx-C9W8qcAhUY1SHBD2Zf1rQ@mail.gmail.com \
--to=jimw@sifive.com \
--cc=gcc-help@gcc.gnu.org \
--cc=tambewilliam@gmail.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).