public inbox for
 help / color / mirror / Atom feed
From: Daniele Testa <>
Subject: How do I define default search paths for gcc and cc1?
Date: Wed, 19 Jun 2019 08:13:00 -0000	[thread overview]
Message-ID: <> (raw)


I am doing a cross-native/canadian toolchain build to later move to my own
Linux distribution:

build  = x86_64-pc-linux-gnu
host   = arm-linux-gnueabihf
target = arm-linux-gnueabihf

The problem I am having is that the resulting "gcc" and "cc1" does not have
default search paths that I require. As an example, the "gcc" is not
looking for "cc1" at the location that I want and "cc1" does not even look
in the standard places, such as "/usr/include".

As I will move the final toolchain to another system with other paths, I
need a way to change these default search paths.

As it stands now, the toolchain is not easily movable. I know that I can
use "gcc -I..." when compiling, but I prefer that "gcc" and "cc1" have
sensible default search paths and not something like "~/x-tools/...".

Any help would be appreciated. Thanks!


                 reply	other threads:[~2019-06-19  8:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).