Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] e2fsprogs: do not use ldconfig when building the host variant
Date: Sun, 9 Sep 2018 15:22:18 +0200	[thread overview]
Message-ID: <20180909152218.1f038fc7@windsurf.home> (raw)
In-Reply-To: <20180831211240.20322-1-thomas.petazzoni@bootlin.com>

Hello,

On Fri, 31 Aug 2018 23:12:39 +0200, Thomas Petazzoni wrote:
> Since commit 93acaa5a573865afc7a8c0912a7037965eb845a6 ("e2fsprogs:
> build shared library for the host"), we are building shared libraries
> in host-e2fsprogs instead of static libraries. A consequence of this
> is that the e2fsprogs build system tries to run ldconfig on the host,
> which fails when running as non-root:
> 
> /usr/sbin/ldconfig: Can't create temporary cache file /etc/ld.so.cache~: Permission denied
> make[3]: [Makefile:441: install-shlibs] Error 1 (ignored)
> 
> Tell the configure script to use "true" as ldconfig in order to avoid
> this problem.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
>  package/e2fsprogs/e2fsprogs.mk | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)

Both patches applied to master.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2018-09-09 13:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31 21:12 [Buildroot] [PATCH 1/2] e2fsprogs: do not use ldconfig when building the host variant Thomas Petazzoni
2018-08-31 21:12 ` [Buildroot] [PATCH 2/2] e2fsprogs: simplify handling of ldconfig for target variant Thomas Petazzoni
2018-09-09 13:22 ` 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=20180909152218.1f038fc7@windsurf.home \
    --to=thomas.petazzoni@bootlin.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