Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Frank Hunleth <fhunleth@troodon-software.com>
Cc: Will Newton <will.newton@gmail.com>, buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] erlang: support builds when gcc __atomic_* exist
Date: Mon, 2 Aug 2021 14:55:44 +0200	[thread overview]
Message-ID: <20210802145544.62e46f99@windsurf> (raw)
In-Reply-To: <CA+-urNS33eBwcaCSTMAb690j7r2M4674MuPkDhEX1X=Qr7YYXQ@mail.gmail.com>

On Mon, 2 Aug 2021 08:46:37 -0400
Frank Hunleth <fhunleth@troodon-software.com> wrote:

> As you expected, a SPARCv8 build fails. I updated erlang.mk to pass
> linker flags to link to libatomic, but still received errors. The
> errors were of type:
> 
> /tmp/cc1Mog0n.s:230: Error: Architecture mismatch on "cas [%g3],%g2,%g1".
> /tmp/cc1Mog0n.s:230: (Requires v9|v9a|v9b|v9c|v9d|v9e|v9v|v9m|m8;
> requested architecture is v8.)
> 
> I ran out of time this morning to track this down (sorry), but it's
> sounding like Erlang is doing something that's not causing function
> calls into libatomic.
> 
> Right now, I'm thinking that trying to be more generic about what
> platforms Erlang supports may not be worth it. I.e., change this:
> 
>         default y if BR2_i386 || BR2_x86_64 || BR2_powerpc || \
>                 BR2_sparc_v9 || BR2_arm || BR2_aarch64 || BR2_mipsel || \
>                 BR2_TOOLCHAIN_HAS_ATOMIC
> 
> to
> 
>         default y if BR2_i386 || BR2_x86_64 || BR2_powerpc || \
>                 BR2_sparc_v9 || BR2_arm || BR2_aarch64 || BR2_mipsel || \
>                 BR2_RISCV_64
> 
> What do you think?

I'm fine with that. Note that it's also causing problems on other CPU
architectures:

  http://autobuild.buildroot.net/?reason=erlang%

You will however see that even on ARM64 there are some failures in
erlang-jiffy.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

      reply	other threads:[~2021-08-02 12:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-08 22:24 [Buildroot] [PATCH 1/1] erlang: support builds when gcc __atomic_* exist Frank Hunleth
2021-07-28 21:35 ` Thomas Petazzoni
2021-08-02 12:46   ` Frank Hunleth
2021-08-02 12:55     ` Thomas Petazzoni [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210802145544.62e46f99@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=fhunleth@troodon-software.com \
    --cc=will.newton@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox