Re: GCC builds with relative searchpaths instead of absolute

[Nuno Silva <little.coding.fox@gmail.com>]

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.

Did you run make install?
Yes, that's the next step actually, and cc1 is located in a libexec
path of my sysroot.

On Wed, Sep 21, 2022 at 1:49 PM Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>
> On Wed, 21 Sept 2022 at 12:43, Nuno Silva via Gcc-help
> <gcc-help@gcc.gnu.org> wrote:
> >
> > Hello,
> > This is my first post in this mailing list, so I apologize if I do
> > anything wrong.
> >
> > I'm working on a hobby operating system and, as part of making apps
> > for it, I'm trying to port gcc to it. To be clear: I already have my
> > cross compiler, I just want to make gcc run inside the OS.
> >
> > However, gcc doesn't seem to find cc1, and when I look into the
> > searchdirs it shows relative paths (prepended with ".."), which means
> > it would never find cc1.
>
> Why not?
>
> > I'm configuring GCC with the following:
> >
> > configure --host=x86_64-toast --prefix=/usr --target=x86_64-toast
> > --with-sysroot=/ --with-build-sysroot=<my sysroot dir>
> > --enable-languages=c,c++ --enable-initfini-array --disable-multilib
> > --disable-nls --enable-lto --with-system-zlib CFLAGS=-O2 CXXFLAGS=-O2
> >
> > Then running make all-gcc all-target-libgcc all-target-libcstdc++-v3
>
> Did you run make install?
> Because that's what installs cc1 and gcc into the right locations so
> that the relative paths work.