From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Nuno Silva <little.coding.fox@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: GCC builds with relative searchpaths instead of absolute
Date: Wed, 21 Sep 2022 14:49:02 +0100 [thread overview]
Message-ID: <CAH6eHdTks=zEnnn3KWU1y0e9GNvtrnR-hWU-8M9P4hGu22=K-w@mail.gmail.com> (raw)
In-Reply-To: <CANLiTtuz-oJFUC3QB1kRO_dYKgOf_bLkzf981cdGEn=FTyMV7g@mail.gmail.com>
On Wed, 21 Sept 2022 at 13:57, Nuno Silva wrote:
>
> Hello Jonathan,
> Why not:
> Possibly I'm missing something on my OS that could be making it not
> know where to find it: Right now it's just trying to run cc1 through
> execve but doesn't pass a path for cc1, just a plan cc1, which fails
> to be found as a result.
OK, I thought you meant that relative paths would mean it can never be found.
In any case, when I run gcc it uses a complete path to cc1:
execve("/home/jwakely/gcc/13/libexec/gcc/x86_64-pc-linux-gnu/13.0.0/cc1", ...)
That is a native compiler, not a cross compiler, but I get the same
behaviour for my cross-compilers.
next prev parent reply other threads:[~2022-09-21 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 11:42 Nuno Silva
2022-09-21 12:49 ` Jonathan Wakely
2022-09-21 12:56 ` Nuno Silva
2022-09-21 13:49 ` Jonathan Wakely [this message]
2022-09-21 13:53 ` Nuno Silva
2022-09-21 15:31 ` AW: " stefan
2022-09-21 15:57 ` Xi Ruoyao
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='CAH6eHdTks=zEnnn3KWU1y0e9GNvtrnR-hWU-8M9P4hGu22=K-w@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=little.coding.fox@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).