Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libtirpc: fix compilation error
Date: Sat, 30 Dec 2017 11:51:17 +0100	[thread overview]
Message-ID: <20171230115117.7b80bb20@windsurf.lan> (raw)
In-Reply-To: <trinity-bca13856-de1a-42f4-a4d4-41193f6eaf92-1514616283921@3c-app-mailcom-bs04>

Hello,

On Sat, 30 Dec 2017 07:44:43 +0100, daggs wrote:

> > I initially couldn't reproduce it, but after thinking more about the
> > problem, I understood what happened: you don't have RPC support
> > installed in your host system. The build of the rpcgen host program
> > fails to build because it can't find those headers, which on my system
> > (or the autobuilder instances) are provided system-wide.  
> weird, I have it too on my system:
> dagg at NCC-5001-D ~ $ ll /usr/include/tirpc/rpc/types.h
> -rw-r--r-- 1 root root 3270 Dec  1 15:44 /usr/include/tirpc/rpc/types.h

Notice how it is in /usr/include/tirpc, while on my system it is in:

$ ls -l /usr/include/rpc/types.h 
-rw-r--r-- 1 root root 3233 Dec  6 18:20 /usr/include/rpc/types.h

So, in your system, a #include <rpc/types.h> doesn't find it, while it
does on my system. I believe it's because on your system, the RPC
implementation comes from libtirpc, while on my system, it comes from
glibc.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2017-12-30 10:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29 13:03 [Buildroot] [PATCH] libtirpc: fix compilation error Dagg Stompler
2017-12-29 13:38 ` Thomas Petazzoni
2017-12-29 14:24   ` daggs
2017-12-29 21:23     ` Thomas Petazzoni
2017-12-30  6:44       ` daggs
2017-12-30 10:51         ` Thomas Petazzoni [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=20171230115117.7b80bb20@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.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