From: Stefan <stefan-guix@vodafonemail.de>
To: Jean-Pierre De Jesus Diaz <jean@foundationdevices.com>,
Attila Lendvai <attila@lendvai.name>
Cc: guix-devel@gnu.org
Subject: Re: A different way to build GCC to overcome issues, especially with C++ for embedded systems
Date: Fri, 22 Dec 2023 10:56:21 +0100 [thread overview]
Message-ID: <c8bc8357-34c6-a5eb-f592-d44e47c38a6d@vodafonemail.de> (raw)
In-Reply-To: <CAG1gdUqF2Vq4bWLSjiFYzPfYuBWDC_AFB0jj96s+dXAMX0EEwg@mail.gmail.com>
Hi Jean-Pierre!
>The arm-none-eabi target is not finished yet since I'm running into some
>issues when building Axoloti which depends on the (gnu packages embedded)
>toolchains and I'm trying to migrate it to use `cross-gcc-toolchain` but it is
>proving a bit difficult due to search paths but I'm trying to solve it anyway.
These include path problems where exactly the problems which I solved with that gcc12 and gcc12-cross packages. Let's say that they are a proof-of-concept for a better way to build GCC, not relying on environment variables for standard include paths. My gut feeling is that the whole GCC version chain starting in (gnu packages commencement) should be build this way, and in the end also the cross-gcc-toolchain would not have these issues. However, I think that would be an enormous effort – a bit like rewriting the bootstrapping of Guix – and I have no clue how to start myself with it.
Bye
Stefan
next prev parent reply other threads:[~2023-12-22 9:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 18:55 A different way to build GCC to overcome issues, especially with C++ for embedded systems Stefan
2023-12-21 13:32 ` Attila Lendvai
2023-12-21 14:01 ` Jean-Pierre De Jesus Diaz
2023-12-22 9:56 ` Stefan [this message]
2023-12-22 9:33 ` Stefan
2023-12-22 10:56 ` Attila Lendvai
-- strict thread matches above, loose matches on Subject: below --
2024-05-18 12:45 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
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=c8bc8357-34c6-a5eb-f592-d44e47c38a6d@vodafonemail.de \
--to=stefan-guix@vodafonemail.de \
--cc=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=jean@foundationdevices.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.
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).