From: Michael J. Hammel <buildroot@graphics-muse.org>
To: buildroot@busybox.net
Subject: [Buildroot] RPC and Busybox
Date: Tue, 26 Jun 2012 20:55:00 -0600 [thread overview]
Message-ID: <1340765700.13686.18.camel@kepler.gfxmuse.org> (raw)
In-Reply-To: <20120627000701.506f534e@skate>
On Wed, 2012-06-27 at 00:07 +0200, Thomas Petazzoni wrote:
> And we unconditionally enable RPC support in the package (for example,
> we tune the Busybox configuration file or other customization).
>
> Other suggestions? Thoughts?
I'm not sure which direction is best, but I have a possibly related
issue. I have a Busybox 1.20.1 configuration that builds correctly
using an external toolchain when built on its own, but when built under
buildroot I get the following:
In file included from util-linux/mount.c:134:0:
/home/mjhammel/src/ximba/bb/src/../bld/buildroot-2012.05.bld/staging//usr/arm-unknown-linux-gnueabi/sysroot/usr/in
clude/rpc/rpc.h:2:28: fatal error: sunrpc/rpc/rpc.h: No such file or
directory
compilation terminated.
make[3]: *** [util-linux/mount.o] Error 1
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?
--
Michael J. Hammel <buildroot@graphics-muse.org>
next prev parent reply other threads:[~2012-06-27 2:55 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 ` Michael J. Hammel [this message]
2012-06-27 7:18 ` [Buildroot] RPC and Busybox Thomas Petazzoni
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=1340765700.13686.18.camel@kepler.gfxmuse.org \
--to=buildroot@graphics-muse.org \
--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