From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] xtensa: disable libffi for Xtensa
Date: Wed, 21 Nov 2012 11:04:09 +0100 [thread overview]
Message-ID: <20121121110409.59547168@skate> (raw)
In-Reply-To: <50ACA0A6.9020507@zankel.net>
Dear Chris Zankel,
On Wed, 21 Nov 2012 01:36:38 -0800, Chris Zankel wrote:
> > You need to recursively propagate this 'depends' to all packages selecting
> > BR2_PACKAGE_LIBFFI. This is due to a limitation of kconfig that doesn't check
> > whether a package is actually selectable.
>
> Ah, good to know. Thanks. Will create another patch.
No, don't do it. You will become crazy before you get to the end of it.
libffi is a dependency for glib and python, and glib in turn has a
crazy number of reverse dependencies, themselves having other
reverse dependencies. You would have to add a depends on !BR2_xtensa on
dozens and dozens of packages.
This is a known limitation of kconfig, which we have discussed in
length during the last Buildroot Developer Days, see point 6) in
http://elinux.org/Buildroot:DeveloperDaysELCE2012#Details_of_the_discussion.
For now, I think it's better to just leave libffi as it is, until we
find a good way of solving the entire problem. We know that we should
ignore those autobuilders failures.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-11-21 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 19:01 [Buildroot] [PATCH 3/3] xtensa: disable libffi for Xtensa Chris Zankel
2012-11-21 8:35 ` Baruch Siach
2012-11-21 9:36 ` Chris Zankel
2012-11-21 10:04 ` 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=20121121110409.59547168@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