I see, then maybe GCC is not finding its base path or something, do
you happen to know where that execve is being called from so I can
investigate the source?
Thank you very much!
On Wed, Sep 21, 2022 at 2:49 PM Jonathan Wakely <jwakely.gcc@xxxxxxxxx> wrote:
>
> 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.
