From: Zane Asher Post <zapost86@gmail.com>
To: gcc-help@gnu.org
Subject: gcc 7.1.0
Date: Mon, 14 Feb 2022 15:40:07 -0600 [thread overview]
Message-ID: <CAGEdSE8M9OMgDirxwwdhn90CDt5XTJircn=EcRo8xD1bcm=cSA@mail.gmail.com> (raw)
Hi. I'm trying to compile a cross compiler to build my OS. I'm trying to
build on Windows using MSYS2. I'm having a couple of issues, though. First,
when it gets to s-selftest in gcc-build/gcc/Makefile, it stops with this
error:
CreateProcess: not a directory or file
It works when I copy cc1.exe into a folder that is in my PATH variable. I'm
afraid that this will mess with my C compiler and the one that is built.
Second, when libgcc is being configured, I get this error:
Cannot compute the suffix of object files
How do I fix these errors?
From, Zane Post
P.S. My configure flags for gcc are:
../gcc-7.1.0/configure --build="aarch64-w64-mingw32" --target="i686-elf"
--prefix="/c/compiled/gcc" --disable-nls --without headers
--enable-languages=c,c++ --without-isl --disable-fixincludes
next reply other threads:[~2022-02-14 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 21:40 Zane Asher Post [this message]
2022-02-14 22:21 ` Tom Kacvinsky
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='CAGEdSE8M9OMgDirxwwdhn90CDt5XTJircn=EcRo8xD1bcm=cSA@mail.gmail.com' \
--to=zapost86@gmail.com \
--cc=gcc-help@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).