From: Ricardo Wurmus <rekado@elephly.net>
To: Jean-Pierre De Jesus Diaz <jean@foundation.xyz>
Cc: "Sergio Pastor Pérez" <sergio.pastorperez@outlook.es>,
"Attila Lendvai" <attila@lendvai.name>,
Stefan <stefan-guix@vodafonemail.de>,
guix-devel@gnu.org
Subject: Re: A different way to build GCC to overcome issues, especially with C++ for embedded systems
Date: Sun, 26 May 2024 00:20:18 +0200 [thread overview]
Message-ID: <87jzjhmt3x.fsf@elephly.net> (raw)
In-Reply-To: <CAG1gdUqRwTmx1uPHsTyL4Ka8wS8-UMWNeEfVGDGARwC7+0YLZA@mail.gmail.com> (Jean-Pierre De Jesus Diaz's message of "Fri, 24 May 2024 17:05:50 +0000")
Jean-Pierre De Jesus Diaz <jean@foundation.xyz> writes:
> I haven't contributed it yet because it has been a bit hard adapting axoloti-*
> packages to use a modern toolchain because I'm also intending to remove
> the old toolchains in `gnu/packages/embedded.scm' eventually and
> instead use the ones in `cross-gcc-toolchain'.
Could you explain why it is difficult to adjust the axoloti/ksoloti
packages? They only need an arm-none-eabi cross-compiler with newlib.
Since I have axoloti boards here, I could test your changes.
--
Ricardo
next prev parent reply other threads:[~2024-05-25 22:21 UTC|newest]
Thread overview: 13+ 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 [this message]
2024-05-27 10:48 ` Jean-Pierre De Jesus Diaz
-- strict thread matches above, loose matches on Subject: below --
2023-10-02 18:55 Stefan
2023-12-21 13:32 ` Attila Lendvai
2023-12-21 14:01 ` Jean-Pierre De Jesus Diaz
2023-12-22 9:56 ` Stefan
2023-12-22 9:33 ` Stefan
2023-12-22 10:56 ` Attila Lendvai
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=87jzjhmt3x.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=jean@foundation.xyz \
--cc=sergio.pastorperez@outlook.es \
--cc=stefan-guix@vodafonemail.de \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.