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: Wed, 24 Apr 2013 16:38:28 +0200	[thread overview]
Message-ID: <20130424163828.5c545de1@skate> (raw)
In-Reply-To: <E6BF041E97966E4DB955F0DF883AD2D6339F9F24@de02wembxa.internal.synopsys.com>

Dear Mischa Jonker,

On Wed, 24 Apr 2013 06:38:29 +0000, Mischa Jonker wrote:

> Yes, it makes perfect sense to add support for ARC here. So this is
> something that we are definitely planning to do in the coming weeks.

Excellent!

> In fact, if you have other suggestions of packages that would require
> specific ARC support, please let me know, so that we can plan for
> these as well (if it makes sense).

From a Buildroot perspective, libffi is really the most annoying
architecture-specific part because it has many, many reverse
dependencies that would all have to be disabled specifically for ARC.
And also because adding a new architecture support in libffi is not
just a matter of adding a few additional defines, it requires a fairly
intimate knowledge of the instruction set and the calling conventions.

The other packages that I can think of that are probably useful when
you start a new architecture are things like strace and ltrace.

But anyway, once the ARC port is in mainline Buildroot, I'll add an ARC
configuration to our autobuilders, and we'll quickly see where the
problems are :-)

Best regards,

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

      reply	other threads:[~2013-04-24 14:38 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 ` [Buildroot] Plan of libffi support? Thomas Petazzoni
2013-04-24  6:38   ` Mischa Jonker
2013-04-24 14:38     ` 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=20130424163828.5c545de1@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