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 13:49:20 +0100 [thread overview]
Message-ID: <CAH6eHdSBsA4fyqHMEN8+scLx77Cfk2S9keATP_ENuWAL-wx50w@mail.gmail.com> (raw)
In-Reply-To: <CANLiTtvvE4dMKvT6pvu4xGrY8cQ+j2MvR2hUi-=b_GP-xwBXXg@mail.gmail.com>
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.
next prev parent reply other threads:[~2022-09-21 12: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 [this message]
2022-09-21 12:56 ` Nuno Silva
2022-09-21 13:49 ` Jonathan Wakely
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=CAH6eHdSBsA4fyqHMEN8+scLx77Cfk2S9keATP_ENuWAL-wx50w@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).