public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: William Tambe <tambewilliam@gmail.com>
To: Jim Wilson <jimw@sifive.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: How to customize GCC builtin search paths
Date: Sun, 12 Apr 2020 12:06:17 -0400	[thread overview]
Message-ID: <CAF8i9mNpK_7iWndtGTxk_-9L61=2rB_Yvv37fi9Ph9vXC0QXiQ@mail.gmail.com> (raw)
In-Reply-To: <CAFyWVaYGYy9-iLaOoNtUkv2HxZv68uG99qvHFhLPXJ-G43qCMQ@mail.gmail.com>

On Fri, Apr 10, 2020 at 1:16 PM Jim Wilson <jimw@sifive.com> wrote:
>
> On Thu, Apr 9, 2020 at 7:52 PM William Tambe via Gcc-help
> <gcc-help@gcc.gnu.org> wrote:
> > How to customize GCC builtin search paths that it uses for %s in its
> > specs syntax ?
>
> This is startfile_prefixes in gcc.c.

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:

#include "..." search starts here:
#include <...> search starts here:
/opt/arch-toolchain/lib/gcc/arch-elf/9.2.0/include
/opt/arch-toolchain/lib/gcc/arch-elf/9.2.0/include-fixed
/opt/arch-toolchain/lib/gcc/arch-elf/9.2.0/../../../../arch-elf/include

However, I am looking to change how gcc looks for includes as follow:

#include "..." search starts here:
#include <...> search starts here:
/opt/arch-toolchain/lib/gcc/arch-elf/9.2.0/../../../../include
/opt/arch-toolchain/lib/gcc/arch-elf/9.2.0/../../../../arch-elf/include
/opt/arch-toolchain/lib/gcc/arch-elf/9.2.0/include
/opt/arch-toolchain/lib/gcc/arch-elf/9.2.0/include-fixed

Any idea what piece of code populate the list of paths where to look
for includes ?

>
> Jim

  reply	other threads:[~2020-04-12 16:06 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 [this message]
2020-04-13 20:44     ` Jim Wilson
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='CAF8i9mNpK_7iWndtGTxk_-9L61=2rB_Yvv37fi9Ph9vXC0QXiQ@mail.gmail.com' \
    --to=tambewilliam@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jimw@sifive.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).