From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] rtptools: needs RPC support
Date: Wed, 23 Sep 2015 14:16:20 +0100 [thread overview]
Message-ID: <5602A624.7020709@imgtec.com> (raw)
In-Reply-To: <20150923151240.31f5d864@free-electrons.com>
Hi Thomas,
On 09/23/2015 02:12 PM, Thomas Petazzoni wrote:
> Hello,
>
> On Wed, 23 Sep 2015 14:07:03 +0100, Vicente Olivert Riera wrote:
>
>>> I'm surprised we have not seen autobuilder failures. Or did you forget
>>> to include a reference to an autobuilder error?
>>
>> No, I didn't forget that. I have catch this issue with one local
>> autobuilder I have. If you wonder why I have a local autobuilder instead
>> of submitting the results to the ML, it's because that autobuilder uses
>> toolchains that are not yet included in our Buildroot tree.
>
> That's perfectly OK. However, I wonder why we haven't seen this problem
> with toolchains already tested in the autobuilders. rtptools does not
> have any other dependencies, and we have a "basic" toolchain with no
> special options enabled.
>
> Also, I think your patch should instead be:
>
> select BR2_PACKAGE_LIBTIRPC if !BR2_TOOLCHAIN_HAS_NATIVE_RPC
I already tried that and it didn't fix the problem. Also added to the
.mk file the following:
ifeq ($(BR2_TOOLCHAIN_HAS_NATIVE_RPC),y)
RTPTOOLS_DEPENDENCIES += libtirpc
endif
After checking that libtirpc was installed, then I ran this command:
find output/staging/ -type f -name "ypclnt.h"
And that file doesn't exist either, so libtirpc can't fix the problem.
Regards,
Vincent.
> and add libtirpc to the dependencies.
>
> Thomas
>
next prev parent reply other threads:[~2015-09-23 13:16 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 [this message]
2015-09-23 13:20 ` Vicente Olivert Riera
2015-09-23 21:25 ` Peter Korsgaard
2015-09-23 21:30 ` Vicente Olivert Riera
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=5602A624.7020709@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 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.