From: Tom Kacvinsky <tkacvins@gmail.com>
To: Zane Asher Post <zapost86@gmail.com>
Cc: gcc-help@gnu.org
Subject: Re: gcc 7.1.0
Date: Mon, 14 Feb 2022 17:21:13 -0500 [thread overview]
Message-ID: <CAG_eJLegQ4Grir=sDzA+tiyic=z95LoNbB9+QL4iCSe0ccrkrQ@mail.gmail.com> (raw)
In-Reply-To: <CAGEdSE8M9OMgDirxwwdhn90CDt5XTJircn=EcRo8xD1bcm=cSA@mail.gmail.com>
On Mon, Feb 14, 2022 at 4:48 PM Zane Asher Post via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> 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
>
I too have had fun with building GCC on Windows using MSYS2. Fortunately
for me, the mingw-w64 development team has been very helpful.
I know of at least one of the mingw-w64 developers chimes in on the binutils
list, perhaps there are some of them on this list, too.
I'd start with this github repo which provides patches for building GCC within
an MSYS2 environment:
https://github.com/msys2/MINGW-packages
There are patches and pacman build scripts (pay attention to the
scripts, they do
some magic aside from applying patches). There is stuff there for arm cross
compilers. But beware, these patches may no longer apply for GCC 7.0 as the
mingw-w64 folks keep pretty current with packages they deliver.
Hope this helps,
Tom
prev parent reply other threads:[~2022-02-14 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 21:40 Zane Asher Post
2022-02-14 22:21 ` Tom Kacvinsky [this message]
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='CAG_eJLegQ4Grir=sDzA+tiyic=z95LoNbB9+QL4iCSe0ccrkrQ@mail.gmail.com' \
--to=tkacvins@gmail.com \
--cc=gcc-help@gnu.org \
--cc=zapost86@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).