Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 18:39:43 -0500	[thread overview]
Message-ID: <511046BF.1070902@gmail.com> (raw)
In-Reply-To: <20130205003238.2ec5aa65@skate>

On 02/04/2013 06:32 PM, Thomas Petazzoni wrote:
> Dear Shawn J. Goff,
>
> On Mon, 04 Feb 2013 17:36:36 -0500, Shawn J. Goff wrote:
>> 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.
> Correct.
>
>> I started to make a patch that allows for explicitly selecting
>> BR2_TOOLCHAIN_HAS_NATIVE_RPC like the external-toolchain allows,
> Seems like the good solution yes.
>
>> 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.
> What problems did you encounter exactly? It should be fairly similar to
> what we do for external toolchains I believe, no?

No problems, it just that when I started down the path, I thought it 
would be just an option, but there turned out to be this whole 
toolchain-checked thing behind it, so I wanted to make sure that is 
what's wanted before I do it.

  reply	other threads:[~2013-02-04 23:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 22:36 [Buildroot] Insufficient RPC options for crosstool-ng toolchain Shawn J. Goff
2013-02-04 23:32 ` Thomas Petazzoni
2013-02-04 23:39   ` Shawn J. Goff [this message]
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=511046BF.1070902@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox