From: Csepp <raingloom@riseup.net>
To: Jean Pierre De Jesus DIAZ <me@jeandudey.tech>
Cc: 57109@debbugs.gnu.org
Subject: bug#57109: arm-none-eabi-toolchain atomic support is broken
Date: Thu, 18 Aug 2022 16:24:01 +0200 [thread overview]
Message-ID: <878rnlbpbe.fsf@riseup.net> (raw)
In-Reply-To: <W3bwtjXOE9kR8_Y5FAONpXogV-HS5-FwbXBLauTFI0N5PN6CVuez0dh2ToQBJGSb02mCOLJ0CPotmEtWG-1LbWZON4no9bk6H1yqT4yeh10=@jeandudey.tech>
Jean Pierre De Jesus DIAZ via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
> The following works though. No newlib or anything:
>
> guix shell --expression='((@ (gnu packages cross-base) cross-gcc) "arm-none-eabi")' -- \
> bash -c "echo '#include <stdatomic.h>' \
> | arm-none-eabi-gcc -x c -o /dev/null -c -"
>
>
> —
> Jean-Pierre De Jesus DIAZ
>
>
> ------- Original Message -------
> On Wednesday, August 10th, 2022 at 1:14 PM, Jean Pierre De Jesus DIAZ <me@jeandudey.tech> wrote:
>
>
>> The atomic supports for this toolchain is broken:
>>
>> A minimal test case:
>>
>> guix shell arm-none-eabi-toolchain -- \
>> bash -c "echo '#include <stdatomic.h>' \
>>
>> | arm-none-eabi-gcc -x c -o /dev/null -c -"
>>
>> Something similar found online:
>>
>> https://sourceware.org/legacy-ml/newlib/2017/msg00150.html
>>
>> However no solution.
>>
>> This happens with all versions of the arm-none-eabi-toolchain
>> packages.
>>
>> —
>> Jean-Pierre De Jesus DIAZ
Might be a good idea to add a (regression) test for this in advance.
Wish I could help, but my expermientation with cross compilation with
Guix were largely fruitless.
prev parent reply other threads:[~2022-08-18 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 11:14 bug#57109: arm-none-eabi-toolchain atomic support is broken Jean Pierre De Jesus DIAZ via Bug reports for GNU Guix
2022-08-16 14:14 ` Jean Pierre De Jesus DIAZ via Bug reports for GNU Guix
2022-08-18 14:24 ` Csepp [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
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=878rnlbpbe.fsf@riseup.net \
--to=raingloom@riseup.net \
--cc=57109@debbugs.gnu.org \
--cc=me@jeandudey.tech \
/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).