All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] nfs-utils build failed
Date: Sun, 20 Feb 2011 22:41:44 +0100	[thread overview]
Message-ID: <87aahqe63r.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <AANLkTi=M1GVWE=+DD5X=T2eeysYDhETsyrisG5W9PPZQ@mail.gmail.com> (Martin Hicks's message of "Sun, 20 Feb 2011 09:20:01 -0500")

>>>>> "Martin" == Martin Hicks <mort@bork.org> writes:

 Martin> 2011/2/20 Zden?k Materna <zdenek.materna@gmail.com>:
 >> Hello,
 >> 
 >> I'm back with another problem which I can't solve. I'm using buildroot from
 >> git, uclibc 0.9.31 and there is some problem with building nfs-utils (build
 >> log at bottom). If I understand it right rpcgen is used to generate mount.h.
 >> But rpcgen is compiled for target and can't be run on host. Then it's little
 >> bit strange that mount.h missing error is produced before "rpcgen: cannot
 >> execute binary file" error.
 >> 
 >> Can anybody explain it for me? I'm quite confused with it. And any tips what
 >> to do to compile nfs-utils?

 Martin> I fought with this in a non buildroot environment this week.  The
 Martin> reason is that rpcgen is compiled with your cross compiler and not
 Martin> your build host's CC.  I couldn't figure out how to make automake use
 Martin> my host's compiler, but did eventually figure out that if you install
 Martin> the rpcgen program from your build server's package manager into
 Martin> /usr/bin  you can specify RPCGEN=/usr/bin/rpcgen and nfs-utils will
 Martin> stop trying to compile this tool and just use the one you've
 Martin> specified.

FYI: I've fixed the nfs-utils package in git to build rpcgen itself, so
you no longer need this.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-02-20 21:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-20 13:03 [Buildroot] nfs-utils build failed Zdeněk Materna
2011-02-20 14:20 ` Martin Hicks
2011-02-20 21:41   ` Peter Korsgaard [this message]
2011-02-21 20:21     ` Zdeněk Materna

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=87aahqe63r.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.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 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.