From: William Tambe <tambewilliam@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: GCC_EXEC_PREFIX or option -B needed to find cc1 and crt*.o files
Date: Sun, 4 Dec 2022 20:46:34 -0600 [thread overview]
Message-ID: <CAF8i9mM6Vkstz1Z94HrL-bHxA_RCA9oFm0k3BtAKUeiWzdSSvQ@mail.gmail.com> (raw)
GCC fails to run with following error:
gcc: fatal error: cannot execute 'cc1': execvp: No such file or directory
Above error goes away when setting environment GCC_EXEC_PREFIX or
using option -B to the path where `cc1` was installed.
GCC was configured as follow:
configure --target=pu32-elf --host=pu32-elf --prefix=/opt/toolchain
--libexecdir=/opt/toolchain/lib --without-headers --disable-libssp
--disable-multilib --disable-gcov --disable-lto --enable-libatomic
--enable-languages=c,c++ --disable-nls --disable-doc --disable-docs
--disable-documentation
Any idea why the correct prefix where to find `cc1` is not built inside GCC ?
Complete change implementing target pu32 can be found at:
https://github.com/fontamsoc/gcc/commit/5a661b4
reply other threads:[~2022-12-05 2:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAF8i9mM6Vkstz1Z94HrL-bHxA_RCA9oFm0k3BtAKUeiWzdSSvQ@mail.gmail.com \
--to=tambewilliam@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/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).