From: Stefan <stefan-guix@vodafonemail.de>
To: "Ekaitz Zarraga" <ekaitz@elenq.tech>,
guix-devel@gnu.org, "Attila Lendvai" <attila@lendvai.name>,
"Sergio Pastor Pérez" <sergio.pastorperez@outlook.es>,
"Timothy Sample" <samplet@ngyro.com>,
janneke@gnu.org
Subject: Re: A different way to bootstrap and build GCC
Date: Sun, 24 Nov 2024 13:02:27 +0100 [thread overview]
Message-ID: <eb1c19bf-4409-42cb-a06f-df27263a3b92@vodafonemail.de> (raw)
In-Reply-To: <Z0LjgTlJdm1-VVMY@3900XT>
Hi Efraim!
> In terms of what I've seen so far from your repo and reading your email
> I would suggest just trying to bump make from 3.80 to 3.82, it Just
> Worked™ for me, even on riscv64.
Yes, you are right, I should drop the use of gnu-make-mesboot0. This would allow me to drop four substitutions in the TCC package. In the original commencement.scm it is anyway bound to i686-unknown-linux-gnu, which I want to avoid. I think I should try version 4.4.1, which I build with the latest TCC anyway.
> Also I had been using musl-1.1.24 as an intermediate step, but with some
> of your code I currently have 1.2.5 built and am testing that out.
Nice!
> For example I ended up rewriting the musl install phase.
Ah, I know about the trouble. I patch the install script a bit. Look for “;; Gash does not support getopts, replace its use.” With that patch the default install phase of musl is working just fine. Maybe I should try to send that patch upstream.
Bye
Stefan
next prev parent reply other threads:[~2024-11-24 12:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 12:45 A different way to build GCC to overcome issues, especially with C++ for embedded systems Sergio Pastor Pérez
2024-05-19 22:06 ` Stefan
2024-05-20 6:59 ` Attila Lendvai
2024-05-24 15:48 ` Sergio Pastor Pérez
2024-05-24 17:05 ` Jean-Pierre De Jesus Diaz
2024-05-25 22:20 ` Ricardo Wurmus
2024-05-27 10:48 ` Jean-Pierre De Jesus Diaz
2024-11-23 23:20 ` A different way to bootstrap and build GCC Stefan
2024-11-23 23:46 ` Ekaitz Zarraga
2024-11-24 8:27 ` Efraim Flashner
2024-11-24 12:02 ` Stefan [this message]
2024-11-24 12:02 ` Stefan
2024-11-24 12:02 ` Rutherther
2024-11-24 21:13 ` Stefan
2024-11-24 12:36 ` Ekaitz Zarraga
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eb1c19bf-4409-42cb-a06f-df27263a3b92@vodafonemail.de \
--to=stefan-guix@vodafonemail.de \
--cc=attila@lendvai.name \
--cc=ekaitz@elenq.tech \
--cc=guix-devel@gnu.org \
--cc=janneke@gnu.org \
--cc=samplet@ngyro.com \
--cc=sergio.pastorperez@outlook.es \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).