Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Revert "toolchain/toolchain-buildroot: enable uclibc for riscv64"
Date: Sat, 15 Aug 2020 22:47:35 +0200	[thread overview]
Message-ID: <20200815224735.6cccee26@windsurf.home> (raw)
In-Reply-To: <20200815203014.GA24264@scaer>

Hello Yann,

On Sat, 15 Aug 2020 22:30:14 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> Applied to master, thanks.
> 
> OTOH, I was wondering why we were not adding an exclusion in the
> genrandconfig script, like we do for all the other libffi limitations...

Our libffi exclusions in genrandconfig are really when there is no
support for a given CPU architecture in libffi.

In the situation we're talking about, libffi does have support for
RISC-V 64-bit. The limitation is not in libffi, but in uClibc-ng.

We could certainly have handled that by an autobuilder exception, but
I've never been a big fan of such autobuilder exceptions. That being
said, if the general feeling is that an autobuilder exception is a
better way of avoiding those build failures, I'm fine with changing to
that solution.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2020-08-15 20:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-15 14:10 [Buildroot] [PATCH] Revert "toolchain/toolchain-buildroot: enable uclibc for riscv64" Thomas Petazzoni
2020-08-15 20:30 ` Yann E. MORIN
2020-08-15 20:47   ` 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=20200815224735.6cccee26@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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