Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Plan of libffi support?
Date: Mon, 22 Apr 2013 18:01:04 +0200	[thread overview]
Message-ID: <20130422180104.2fd1513d@skate> (raw)
In-Reply-To: <1366630651-6857-1-git-send-email-mjonker@synopsys.com>

Dear Mischa Jonker,

On Mon, 22 Apr 2013 13:37:24 +0200, Mischa Jonker wrote:

> In the following patch series I've added ARC support to the "master" tree
> of BuildRoot. As ARC support is not yet in all upstream open source packages,
> I've taken the freedom to add an option for an additional download site, from
> which ARC-specific versions of gcc, binutils, etc. can be downloaded.
> 
> ARC will be in Linux 3.9, so that would be the first package that can be
> removed from this ARC-specific download site.
> 
> The below patchset builds the toolchain, and a working root file system. Most
> simple packages build OK, but mplayer for instance does not have ARC support,
> and there are probably others as well.
> 
> Could you please have a look at the patches and let me know what to do to
> make them BuildRoot-worthy?

Do you have plans to get ARC support in libffi
<http://sourceware.org/libffi/> ? This library requires some
architecture-specific bits, and is used as a dependency for the Python
interpreter, but also more importantly for the glib library from the
Gtk world. And this glib library is used as a dependency in gazillions
of packages: Gtk+, GStreamer, Bluez-utils, Connman, and many, many more
things. For this reason, having an architecture supported in Buildroot
that doesn't have libffi support is a big pain, because we have to add
the "depends on !BR2_arc && !BR2_arceb" on all the packages that have
Glib as a dependency in their dependency chain.

So, we can live for a while without libffi support, but it would be
good to know if libffi support is somewhere in your plans in the future.

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2013-04-22 16:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 11:37 [Buildroot] [PATCH 0/7] RFC: ARC port Mischa Jonker
2013-04-22 11:37 ` [Buildroot] [PATCH 1/7] arc: Add ARC and ARC BE architecture Mischa Jonker
2013-04-22 15:47   ` Thomas Petazzoni
2013-04-22 18:40   ` Arnout Vandecappelle
2013-04-22 11:37 ` [Buildroot] [PATCH 2/7] arc: Add option for ARC-specific download site Mischa Jonker
2013-04-22 15:48   ` Thomas Petazzoni
2013-04-22 18:25     ` Arnout Vandecappelle
2013-04-22 11:37 ` [Buildroot] [PATCH 3/7] arc: Add support for ARC-specific binutils Mischa Jonker
2013-04-22 15:49   ` Thomas Petazzoni
2013-04-22 18:35   ` Arnout Vandecappelle
2013-04-22 18:36   ` Arnout Vandecappelle
2013-04-22 11:37 ` [Buildroot] [PATCH 4/7] arc: Add ARC specific kernel headers Mischa Jonker
2013-04-22 15:52   ` Thomas Petazzoni
2013-04-22 11:37 ` [Buildroot] [PATCH 5/7] arc: Add support for ARC-specific GCC Mischa Jonker
2013-04-22 15:56   ` Thomas Petazzoni
2013-04-24 12:44     ` Mischa Jonker
2013-04-24 14:27       ` Thomas Petazzoni
2013-04-24 15:19         ` Mischa Jonker
2013-04-24 21:19           ` Yann E. MORIN
2013-04-22 11:37 ` [Buildroot] [PATCH 6/7] arc: Add support for ARC-specific uClibc Mischa Jonker
2013-04-22 15:56   ` Thomas Petazzoni
2013-04-22 11:37 ` [Buildroot] [PATCH 7/7] arc: Make sure that libgcc doesn't get included when it doesn't exist yet Mischa Jonker
2013-04-22 15:57   ` Thomas Petazzoni
2013-04-22 15:46 ` [Buildroot] [PATCH 0/7] RFC: ARC port Thomas Petazzoni
2013-04-22 16:01 ` Thomas Petazzoni [this message]
2013-04-24  6:38   ` [Buildroot] Plan of libffi support? Mischa Jonker
2013-04-24 14:38     ` Thomas Petazzoni

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=20130422180104.2fd1513d@skate \
    --to=thomas.petazzoni@free-electrons.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