From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] libtirpc: prevent selection when ADI Blackfin external toolchains are used
Date: Tue, 28 May 2013 21:45:35 +0200 [thread overview]
Message-ID: <1369770335-6995-3-git-send-email-thomas.petazzoni@free-electrons.com> (raw)
In-Reply-To: <1369770335-6995-1-git-send-email-thomas.petazzoni@free-electrons.com>
libtirpc fails to build with the Blackfin external toolchains provided
by Analog Devices, because their uClibc configuration doesn't include
AI_ADDRCONFIG. In order to prevent such build failures to happen, we
simply prevent libtirpc from being selected when such toolchains are
used. This is not a big problem, since they provide native RPC
support.
Also, since they provide native RPC, we don't have to propagate this
new dependency to the reverse dependencies of libtirpc, because they
all use native RPC when available. The exception to this rule is the
rpcbind package, which can only use the libtirpc implementation of
RPCs, and not the native one of C libraries. Therefore, the dependency
is propagated to the rpcbind package.
Fixes:
http://autobuild.buildroot.org/results/58b/58b16449065c16afce11ba120db56839efb2b1ea/build-end.log
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
---
package/libtirpc/Config.in | 7 +++++++
package/rpcbind/Config.in | 4 ++++
2 files changed, 11 insertions(+)
diff --git a/package/libtirpc/Config.in b/package/libtirpc/Config.in
index 7e891b4..b9db5aa 100644
--- a/package/libtirpc/Config.in
+++ b/package/libtirpc/Config.in
@@ -1,5 +1,12 @@
config BR2_PACKAGE_LIBTIRPC
bool "libtirpc"
+ # uClibc toolchains provided by ADI don't have AI_ADDRCONFIG
+ # support. Note that since they provide native RPC support, we
+ # don't need to propagate this dependency to reverse
+ # dependencies of libtirpc for which native RPC support can be
+ # used instead of libtirpc.
+ depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R2 && \
+ !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R1
help
Libtirpc is a port of Sun's Transport-Independent RPC
library to Linux.
diff --git a/package/rpcbind/Config.in b/package/rpcbind/Config.in
index 1bdcd9e..cbe53af 100644
--- a/package/rpcbind/Config.in
+++ b/package/rpcbind/Config.in
@@ -3,6 +3,10 @@ config BR2_PACKAGE_RPCBIND
# We really need libtirpc and can't work with the native RPC
# implementation of toolchains.
select BR2_PACKAGE_LIBTIRPC
+ # uClibc toolchains provided by ADI don't have AI_ADDRCONFIG
+ # support, needed for libtirpc
+ depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R2 && \
+ !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R1
help
The rpcbind utility is a server that converts RPC program numbers
into universal addresses.
--
1.7.9.5
next prev parent reply other threads:[~2013-05-28 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 19:45 [Buildroot] [PATCH 0/2] Fix problems related to Blackfin lacking AI_ADDRCONFIG Thomas Petazzoni
2013-05-28 19:45 ` [Buildroot] [PATCH 1/2] czmq: prevent selection when ADI Blackfin external toolchains are used Thomas Petazzoni
2013-05-29 19:21 ` Peter Korsgaard
2013-05-28 19:45 ` Thomas Petazzoni [this message]
2013-05-29 19:22 ` [Buildroot] [PATCH 2/2] libtirpc: " Peter Korsgaard
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=1369770335-6995-3-git-send-email-thomas.petazzoni@free-electrons.com \
--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 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.