All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 1/1] libffi: v3.2.1 doesn't support riscv targets yet
Date: Wed, 24 Oct 2018 10:36:37 +0200	[thread overview]
Message-ID: <20181024103637.487f6190@windsurf> (raw)
In-Reply-To: <81a2a99d-9d72-7821-e7c1-9a09d76d77e5@mind.be>

Hello,

+Mark Corbin in Cc.

On Wed, 24 Oct 2018 01:24:09 +0100, Arnout Vandecappelle wrote:

> > The upcoming version 3.3.0 will support riscv [1], so this patch would
> > be temporary. Do we wait for that release, or should we explicitly
> > disable libffi for riscv in the meantime?
> > 
> > [1] https://github.com/libffi/libffi/commit/3840d49aaa831d649b1597518a2903dfed0d57f3  

FYI, we already discussed the libffi/RISC-V situation during the
Buildroot meeting last week end with Mark Corbin (who added the RISC-V
64 support). And I think he was working on backporting the RISC-V
libffi support so that we can add it as a patch in Buildroot.

That being said...

>  Personally, I would be fine with doing this gradually, i.e. it is not needed to
> fix all 150 packages in a single commit. Indeed, the build is already broken
> anyway, so if this is shown as a circular dependency warning or as a build
> failure of libffi doesn't matter that much.

... I am indeed not opposed to fixing properly the libffi arch
dependencies. It is true that with the autobuilders in place, we can do
this gradually. It would be cleaner than the magic exception we have in
the autobuilder script. The downside is that we will have for a fairly
long time a significant number of autobuilder failures.

Best regards,

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

  parent reply	other threads:[~2018-10-24  8:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23 21:44 [Buildroot] [RFC PATCH 1/1] libffi: v3.2.1 doesn't support riscv targets yet Ferdinand van Aartsen
2018-10-24  0:24 ` Arnout Vandecappelle
2018-10-24  0:26   ` Arnout Vandecappelle
2018-10-24  8:36   ` Thomas Petazzoni [this message]
2018-10-24  8:41     ` Mark Corbin
2018-10-25 10:45       ` Alistair Francis
2018-10-24 13:16     ` Arnout Vandecappelle
2018-10-24 10:10   ` Ferdinand van Aartsen

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=20181024103637.487f6190@windsurf \
    --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 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.