All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] libtirpc: bump to version 1.0.1
Date: Tue, 24 Nov 2015 19:43:01 +0100	[thread overview]
Message-ID: <20151124194301.5dd9ece4@free-electrons.com> (raw)
In-Reply-To: <1446712210-14129-3-git-send-email-peda@lysator.liu.se>

Dear Peter Rosin,

On Thu,  5 Nov 2015 09:30:10 +0100, Peter Rosin wrote:
> From: Peter Rosin <peda@axentia.se>
> 
> Adjust patch 0001 to trivial changes.
> Adjust patch 0007 to remove new DES things.
> Add patch 0008 directly from upstream to fix a late problem in the
> 1.0.1 release.
> 
> Signed-off-by: Peter Rosin <peda@axentia.se>

This patch breaks the build of libtirpc, with the following error:

rpc_soc.c:64:24: fatal error: rpcsvc/nis.h: No such file or directory
compilation terminated.
Makefile:749: recipe for target 'libtirpc_la-rpc_soc.lo' failed
make[4]: *** [libtirpc_la-rpc_soc.lo] Error 1
make[4]: *** Waiting for unfinished jobs....
Makefile:552: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
Makefile:413: recipe for target 'all' failed
make[2]: *** [all] Error 2
package/pkg-generic.mk:188: recipe for target '/home/thomas/projets/buildroot/output/build/libtirpc-1.0.1/.stamp_built' failed
make[1]: *** [/home/thomas/projets/buildroot/output/build/libtirpc-1.0.1/.stamp_built] Error 2
Makefile:36: recipe for target '_all' failed
make: *** [_all] Error 2

Without this patch applied, it builds fine. The failing configuration
is:

BR2_arm=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y
BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-arm-full-2015.11-rc1-71-g90d1299.tar.bz2"
BR2_TOOLCHAIN_EXTERNAL_GCC_4_7=y
BR2_TOOLCHAIN_EXTERNAL_HEADERS_3_10=y
BR2_TOOLCHAIN_EXTERNAL_LOCALE=y
# BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG is not set
BR2_TOOLCHAIN_EXTERNAL_INET_RPC=y
BR2_TOOLCHAIN_EXTERNAL_CXX=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
BR2_PACKAGE_RPCBIND=y
# BR2_TARGET_ROOTFS_TAR is not set

Can you look into this? Once fixed, maybe you can resend the series,
and fix the permission problem in PATCH 1/2 at the same time?

Thanks a lot!

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

  parent reply	other threads:[~2015-11-24 18:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05  8:30 [Buildroot] [PATCH 0/2] bump libtirpc to 1.0.1 Peter Rosin
2015-11-05  8:30 ` [Buildroot] [PATCH 1/2] rpcbind: backport adjustment to changes in libtirpc 1.0.1 Peter Rosin
2015-11-06  8:27   ` Peter Rosin
2015-11-05  8:30 ` [Buildroot] [PATCH 2/2] libtirpc: bump to version 1.0.1 Peter Rosin
2015-11-08 13:30   ` Brendan Heading
2015-11-08 13:37     ` Thomas Petazzoni
2015-11-15  7:43       ` Peter Rosin
2015-11-16 22:08         ` Thomas Petazzoni
2015-11-24 18:43   ` Thomas Petazzoni [this message]
2015-11-24 21:52     ` Peter Rosin
2015-11-24 22:08       ` Thomas Petazzoni
2015-11-24 22:12         ` Peter Rosin
2015-11-25  8:05           ` Thomas Petazzoni
2015-11-05  9:05 ` [Buildroot] [PATCH 0/2] bump libtirpc to 1.0.1 Thomas Petazzoni
2015-11-05 10:44   ` Peter Rosin
2015-11-06  8:06     ` Peter Rosin

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=20151124194301.5dd9ece4@free-electrons.com \
    --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 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.