From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] rtptools: disable for MIPS Codescape toolchains
Date: Tue, 8 Mar 2016 16:03:56 +0000 [thread overview]
Message-ID: <56DEF7EC.20904@imgtec.com> (raw)
In-Reply-To: <20160308163256.764be70e@free-electrons.com>
Hello Thomas,
On 08/03/16 15:32, Thomas Petazzoni wrote:
> Vicente,
>
> On Tue, 8 Mar 2016 14:23:03 +0000, Vicente Olivert Riera wrote:
>> Codescape toolchains don't provide rpcsvc/ypclnt.h, therefore rtptools
>> fails to build showing an error like this one:
>>
>> host2ip.c:13:38: fatal error: rpcsvc/ypclnt.h: No such file or directory
>> #include <rpcsvc/ypclnt.h> /* YP */
>>
>> Fixes:
>>
>> http://autobuild.buildroot.net/results/5a8abdd4918a721c1bddbf68a16d99bea90a59a9/
>>
>> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
>
> Isn't the problem that the Codescape toolchain don't provide RPC
> support at all ?
Yes, that's the problem.
> Or is it really a bug limited to <rpcsvc/ypclnt.h>.
>
> I don't really like to add random toolchain exclusions without a more
> serious explanation than "header file is not in toolchain".
Ok. Perhaps we should make rtptools package depeding on
BR2_TOOLCHAIN_HAS_NATIVE_RPC?
Regards,
Vincent.
>
> Thomas
>
next prev parent reply other threads:[~2016-03-08 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 14:23 [Buildroot] [PATCH] rtptools: disable for MIPS Codescape toolchains Vicente Olivert Riera
2016-03-08 15:32 ` Thomas Petazzoni
2016-03-08 16:03 ` Vicente Olivert Riera [this message]
2016-03-08 16:11 ` Thomas Petazzoni
2016-03-09 14:00 ` Vicente Olivert Riera
2016-03-09 14:05 ` Thomas Petazzoni
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=56DEF7EC.20904@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.