From: Shawn J. Goff <shawn7400@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Insufficient RPC options for crosstool-ng toolchain
Date: Mon, 04 Feb 2013 17:36:36 -0500 [thread overview]
Message-ID: <511037F4.8090906@gmail.com> (raw)
I'm getting an error about a missing rpc_msg.h while building
conntrack-tools. That package selects libtirpc if
!BR2_TOOLCHAIN_HAS_NATIVE_RPC. I'm having BR build the toolchain using
ct-ng; I looked at the toolchain-crosstool-ng/Config.in and it selects
BR2_TOOLCHAIN_HAS_NATIVE_RPC because the ct-ng config that ships with BR
uses glibc 2.9. My ct-ng config uses glibc 2.14, which doesn't have
native RPC support.
I started to make a patch that allows for explicitly selecting
BR2_TOOLCHAIN_HAS_NATIVE_RPC like the external-toolchain allows, but I
ran across check_glibc function and the ext-toolchain-checked stamp and
it looks like quite a lot, so I wanted to find out if you actually want
all that for this fix.
next reply other threads:[~2013-02-04 22:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 22:36 Shawn J. Goff [this message]
2013-02-04 23:32 ` [Buildroot] Insufficient RPC options for crosstool-ng toolchain Thomas Petazzoni
2013-02-04 23:39 ` Shawn J. Goff
2013-02-04 23:49 ` Thomas Petazzoni
2013-02-06 22:06 ` Yann E. MORIN
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=511037F4.8090906@gmail.com \
--to=shawn7400@gmail.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.