From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] /etc/ld.so.conf and /etc/ld.so.conf.d in buildroot target skeleton
Date: Tue, 21 Sep 2010 07:51:18 +0100 [thread overview]
Message-ID: <20100921075118.5a58154a@surf> (raw)
In-Reply-To: <AANLkTi=V6mNKXRM=c5KJHugtVyqai3At-sp5fQ8mFiTu@mail.gmail.com>
Hello,
On Sun, 19 Sep 2010 16:39:24 +0200
Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> wrote:
> That looks like a good solution.
> In case of uClibc though, the parsing of ld.so.conf is a configurable
> option (LDSO_CACHE_SUPPORT), so before generating an ld.so.conf we
> should check whether that option is set.
We don't really support any other uClibc configuration than the one we
ship in toolchain/uClibc/uClibc-x.y.z.config. If an user changes the
configuration we provide, (s)he has to be ready for some build
breakage, because we are testing the build of all packages only with
this specific uClibc configuration. I don't think we can sanely enter
the game that would consist in handling all possible uClibc
configurations to know which packages need what.
Concerning LDSO cache, the LDSO_CACHE_SUPPORT is disabled in our
default configuration.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-09-21 6:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 11:28 [Buildroot] /etc/ld.so.conf and /etc/ld.so.conf.d in buildroot target skeleton Thomas De Schampheleire
2010-09-16 11:41 ` Lionel Landwerlin
2010-09-16 17:30 ` Thomas De Schampheleire
2010-09-16 17:47 ` Lionel Landwerlin
2010-09-19 10:44 ` Thomas De Schampheleire
2010-09-19 11:19 ` Lionel Landwerlin
2010-09-19 14:39 ` Thomas De Schampheleire
2010-09-21 6:51 ` Thomas Petazzoni [this message]
2010-09-21 7:02 ` Thomas De Schampheleire
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=20100921075118.5a58154a@surf \
--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