public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: LIU Hao <lh_mouse@126.com>
To: peter0x44 <peter0x44@disroot.org>, gcc-help@gcc.gnu.org
Subject: Re: Building the latest master GCC using msys2.
Date: Tue, 19 Mar 2024 17:24:47 +0800	[thread overview]
Message-ID: <cac20571-abaa-4408-b5a0-d1c3a368a123@126.com> (raw)
In-Reply-To: <526d894f0fc7ea87db5354d416c29b07@disroot.org>


[-- Attachment #1.1: Type: text/plain, Size: 1203 bytes --]

在 2024-03-17 01:53, peter0x44 via Gcc-help 写道:
> I tried without passing any sysroot, and with --sysroot=/mingw64.
> There appears to be no directory named "mingw" present on the root.
> There is only "mingw64", "mingw32", "ucrt64", etc.
> 
> Does anyone know what I'm doing wrong? Is there something I don't understand about the purpose of 
> --with-sysroot?

Please clone this repo:

   https://github.com/lhmouse/MINGW-packages/

and use these commands to build GCC:

   cd MINGW-packages/mingw-w64-gcc
   MINGW_ARCH=mingw64 makepkg-mingw


If you omit `MINGW_ARCH` it builds for all architectures. You may specify multiple architectures so 
they are built one by one, like

   MINGW_ARCH='mingw64 ucrt64' makepkg-mingw

---

If you need to build the master branch, change

   _branch=releases/gcc-13

to

   _branch=master


However some patches may no longer apply. You may need to cd into the `src` directory, apply those 
patches with `git am -3`, resolve any conflicts, commit the result with `git am --continue`, 
re-create patches with `git format-patch`, copy them back, then update checksums with `updpkgsums`...


-- 
Best regards,
LIU Hao


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2024-03-19  9:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-16 17:53 peter0x44
2024-03-19  9:24 ` LIU Hao [this message]
2024-03-19 11:14   ` Peter0x44

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=cac20571-abaa-4408-b5a0-d1c3a368a123@126.com \
    --to=lh_mouse@126.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=peter0x44@disroot.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).