From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] RPC.h and busybox
Date: Wed, 31 Oct 2012 15:31:01 +0100 [thread overview]
Message-ID: <20121031153101.41b26063@skate> (raw)
In-Reply-To: <20121031114118.GF30343@sapphire.tkos.co.il>
On Wed, 31 Oct 2012 13:41:18 +0200, Baruch Siach wrote:
> > Does anybody have any solution?
>
> This is a toolchain level problem. Either downgrade to a toolchain with 2.13
> glibc, or use a toolchain with tirpc.
I have posted a patch set some time ago that fixes this. It tells
Buildroot whether the toolchain has RPC support or not (even for
glibc/eglibc toolchains), and then is capable of building libtirpc when
the toolchain does not provide RPC support.
I intend to adjust a few things and update it, before resending it.
Maybe before the Buildroot meeting this week-end, maybe after.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-10-31 14:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 11:32 [Buildroot] RPC.h and busybox Alexander Khryukin
2012-10-31 11:41 ` Baruch Siach
2012-10-31 11:56 ` Alexander Khryukin
2012-10-31 12:13 ` Yann E. MORIN
2012-10-31 12:19 ` Alexander Khryukin
2012-10-31 12:13 ` Baruch Siach
2012-10-31 12:28 ` Alexander Khryukin
2012-10-31 14:31 ` Thomas Petazzoni [this message]
2012-10-31 14:52 ` Baruch Siach
2012-10-31 14:58 ` Gustavo Zacarias
2012-10-31 15:00 ` Baruch Siach
2012-10-31 15:28 ` Alexander Khryukin
2012-10-31 17:56 ` Yann E. MORIN
2012-10-31 18:54 ` Thomas Petazzoni
2012-10-31 18:44 ` Thomas Petazzoni
2012-10-31 18:19 ` Paul Chavent
2012-10-31 18:24 ` 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=20121031153101.41b26063@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