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: Fri, 23 Oct 2015 10:26:45 +0200 [thread overview]
Message-ID: <20151023102645.0b8f3729@free-electrons.com> (raw)
In-Reply-To: <CAEYzJUEvAp4sfaykkY8dKi8_9G1YGLZ-3U=dgHj9HR3EHsUKXQ@mail.gmail.com>
Dear Bj?rn Forsman,
On Fri, 23 Oct 2015 09:12:02 +0200, Bj?rn Forsman wrote:
> If you want to completely remove use of (host) /sbin/ldconfig, that's fine too.
>
> Just tell me what to do :-)
We need to completely remove the ldconfig stuff, since it simply cannot
work. However, there is at least one package (mysql) that installs
libraries in a non-standard location (/usr/lib/mysql) and relies on
ld.so.conf for the dynamic linker to find them. I believe we need to
fix MySQL so that it installs its libraries in /usr/lib, and then get
rid of all the ldconfig/ld.so.conf stuff.
Or, alternatively, see how to get it working with an init script which
runs ldconfig at boot time. But then you have to look at how uClibc and
musl handle this, and implement a solution that works for all three C
libraries.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-10-23 8:26 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 [this message]
2015-10-23 12:06 ` Bjørn Forsman
2015-12-29 20:32 ` 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=20151023102645.0b8f3729@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