* How do I define default search paths for gcc and cc1?
@ 2019-06-19 8:13 Daniele Testa
0 siblings, 0 replies; only message in thread
From: Daniele Testa @ 2019-06-19 8:13 UTC (permalink / raw)
I am doing a cross-native/canadian toolchain build to later move to my own
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!
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-06-19 8:13 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-19 8:13 How do I define default search paths for gcc and cc1? Daniele Testa
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).