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 1/2] Makefile: use root-relative -f path for /sbin/ldconfig
Date: Tue, 29 Dec 2015 21:32:16 +0100	[thread overview]
Message-ID: <20151229213216.08a102cc@free-electrons.com> (raw)
In-Reply-To: <1445502151-25735-1-git-send-email-bjorn.forsman@gmail.com>

Bj?rn,

On Thu, 22 Oct 2015 10:22:30 +0200, Bj?rn Forsman wrote:

> $(TARGET_CROSS)ldconfig behaves differently (at least the ldconfig I
> tested, which was built by Buildroot) and should not have root-relative
> -f path. If it does, it will pick up host /etc/ld.so.conf file.
> 
> Signed-off-by: Bj?rn Forsman <bjorn.forsman@gmail.com>
> ---
>  Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

As we discussed previously, our ldconfig handling is broken. So we are
simply planning to remove entirely. I have just posted a patch to this
effect:

	https://patchwork.ozlabs.org/patch/561618/

The idea is that from now on, packages are expected to install
libraries in path that are in the default search path of the dynamic
linker.

Consequently, I've marked your patches as Superseded. If you find any
package that doesn't work properly following our ldconfig removal, do
not hesitate to let us know.

Thanks!

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

      parent reply	other threads:[~2015-12-29 20:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22  8:22 [Buildroot] [PATCH 1/2] Makefile: use root-relative -f path for /sbin/ldconfig Bjørn Forsman
2015-10-22  8:22 ` [Buildroot] [PATCH 2/2] Makefile: add -C flag " Bjørn Forsman
2015-10-22 21:19 ` [Buildroot] [PATCH 1/2] Makefile: use root-relative -f path " Arnout Vandecappelle
2015-10-23  7:12   ` Bjørn Forsman
2015-10-23  8:26     ` Thomas Petazzoni
2015-10-23 12:06       ` Bjørn Forsman
2015-12-29 20:32 ` 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=20151229213216.08a102cc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox