From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] RPC and Busybox
Date: Wed, 27 Jun 2012 09:18:51 +0200 [thread overview]
Message-ID: <20120627091851.72559c7a@skate> (raw)
In-Reply-To: <1340765700.13686.18.camel@kepler.gfxmuse.org>
Le Tue, 26 Jun 2012 20:55:00 -0600,
"Michael J. Hammel" <buildroot@graphics-muse.org> a ?crit :
> I'm not sure what to look for here. I'm using glibc toolchain built
> with Crosstool-NG 1.15.1, Busybox 1.20.1, Buildroot 2012.05. It
> doesn't look like there is a sunrpc/rpc/rpc.h in the toolchain.
>
> Any thoughts on what I should look at here?
Which glibc version are you using? Most likely, you're using glibc 2.14
or 2.15, which don't have RPC support, as was discussed in my e-mail.
For now, there is no solution besides reverting to glibc 2.13, until we
get libtirpc packaged and integrated into Buildroot.
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-06-27 7:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 22:07 [Buildroot] RPC support for modern (e)glibc toolchains Thomas Petazzoni
2012-06-27 2:55 ` [Buildroot] RPC and Busybox Michael J. Hammel
2012-06-27 7:18 ` Thomas Petazzoni [this message]
2012-06-27 8:25 ` [Buildroot] RPC support for modern (e)glibc toolchains Thomas Petazzoni
2012-06-27 11:00 ` Gustavo Zacarias
2012-06-27 12:53 ` Thomas Petazzoni
2012-06-28 11:51 ` Gustavo Zacarias
2012-06-28 11:57 ` Thomas Petazzoni
2012-06-28 12:06 ` Gustavo Zacarias
2012-06-30 12:24 ` Arnout Vandecappelle
2012-07-03 19:48 ` Thomas Petazzoni
2012-07-03 20:37 ` Arnout Vandecappelle
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=20120627091851.72559c7a@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