From: Chris Zankel <chris@zankel.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] xtensa: disable libffi for Xtensa
Date: Tue, 20 Nov 2012 11:01:49 -0800 [thread overview]
Message-ID: <50ac8f69.6548420a.6f5c.2a1b@mx.google.com> (raw)
Xtensa currently doesn't support libffi.
Signed-off-by: Chris Zankel <chris@zankel.net>
---
package/libffi/Config.in | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/libffi/Config.in b/package/libffi/Config.in
index 7211f8f..4afb669 100644
--- a/package/libffi/Config.in
+++ b/package/libffi/Config.in
@@ -1,5 +1,6 @@
config BR2_PACKAGE_LIBFFI
bool "libffi"
+ depends on !BR2_xtensa
help
The libffi library provides a portable, high level
programming interface to various calling conventions. This
--
1.7.9.5
next reply other threads:[~2012-11-20 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 19:01 Chris Zankel [this message]
2012-11-21 8:35 ` [Buildroot] [PATCH 3/3] xtensa: disable libffi for Xtensa Baruch Siach
2012-11-21 9:36 ` Chris Zankel
2012-11-21 10:04 ` 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=50ac8f69.6548420a.6f5c.2a1b@mx.google.com \
--to=chris@zankel.net \
--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