From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] rtptools: needs RPC support
Date: Wed, 23 Sep 2015 22:30:19 +0100 [thread overview]
Message-ID: <560319EB.8080003@imgtec.com> (raw)
In-Reply-To: <87pp18q14y.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On 23/09/15 22:25, Peter Korsgaard wrote:
>>>>>> "Vicente" == Vicente Olivert Riera <Vincent.Riera@imgtec.com> writes:
>
> > rtptools needs a toolchain with RPC support, otherwise it will fail with
> > an error message like this one:
>
> > host2ip.c:13:38: fatal error: rpcsvc/ypclnt.h: No such file or directory
> > #include <rpcsvc/ypclnt.h> /* YP */
>
> Hmm, are you sure?
>
> I just did a test build here with a toolchain without RPC support:
>
> find output/staging/usr -name ypclnt.h
>
> But it still built. I do see that rpctools itself contain that header
> file:
>
> find output/build/rtptools-1.20 -name ypclnt.h
> output/build/rtptools-1.20/nt/include/ypclnt.h
> output/build/rtptools-1.20/nt/include/rpcsvc/ypclnt.h
>
We were discussing about this in the IRC during this afternoon, and
checked that it actually builds with toolchains without RPC. I
highlighted the issue using a toolchain which is a bit special.
I then marked my patch as deferred few hours ago, but now I'm going to
mark it as rejected. I will keep investigating about this because is
very weird that the rtptools itself has the headers but my toolchain is
not able to find them.
Regards,
Vincent.
prev parent reply other threads:[~2015-09-23 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 11:57 [Buildroot] [PATCH] rtptools: needs RPC support Vicente Olivert Riera
2015-09-23 13:03 ` Thomas Petazzoni
2015-09-23 13:07 ` Vicente Olivert Riera
2015-09-23 13:12 ` Thomas Petazzoni
2015-09-23 13:16 ` Vicente Olivert Riera
2015-09-23 13:20 ` Vicente Olivert Riera
2015-09-23 21:25 ` Peter Korsgaard
2015-09-23 21:30 ` Vicente Olivert Riera [this message]
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=560319EB.8080003@imgtec.com \
--to=vincent.riera@imgtec.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