From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] skeleton: add support for /etc/ld.so.conf.d/*.conf files
Date: Fri, 31 Oct 2014 16:41:56 +0100 [thread overview]
Message-ID: <20141031164156.6a386482@free-electrons.com> (raw)
In-Reply-To: <1414768749-15134-1-git-send-email-jezz@sysmic.org>
Dear J?r?me Pouiller,
On Fri, 31 Oct 2014 16:19:07 +0100, J?r?me Pouiller wrote:
> +ifeq ($(BR2_TOOLCHAIN_USES_MUSL),y)
> +define GENERATE_LD_SO_CONF_FILE
> + ls $(TARGET_DIR)/etc/ld.so.conf.d/*.conf > /dev/null 2>&1 && \
> + echo "Usage of /etc/ld.so.conf.d/*.conf files with musl libc is not supported"
We should error out here.
Does musl supports /etc/ld.so.conf ? If so, then I believe we should
simply not use the /etc/ld.so.conf.d/ feature of glibc, and instead
keep using /etc/ld.so.conf only, like MySQL was doing.
If you don't want to see repeated entries, you can do something like:
grep -q "^/usr/lib/mysql$" $(TARGET_DIR)/etc/ld.so.conf ||
echo "/usr/lib/mysql" >> $(TARGET_DIR)/etc/ld.so.conf
We could even imagine having a make function to do that.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-31 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 15:19 [Buildroot] [PATCH v2 1/3] skeleton: add support for /etc/ld.so.conf.d/*.conf files Jérôme Pouiller
2014-10-31 15:19 ` [Buildroot] [PATCH v2 2/3] gst-fsl-plugins: fix plugins loading Jérôme Pouiller
2014-10-31 15:37 ` Thomas Petazzoni
2014-10-31 15:19 ` [Buildroot] [PATCH v2 3/3] mysql: use /etc/ld.so.conf.d instead of /etc/ld.so.conf Jérôme Pouiller
2014-10-31 15:39 ` Thomas Petazzoni
2014-10-31 15:41 ` Thomas Petazzoni [this message]
2014-10-31 16:06 ` [Buildroot] [PATCH v2 1/3] skeleton: add support for /etc/ld.so.conf.d/*.conf files Jérôme Pouiller
2014-11-01 16:39 ` Yann E. MORIN
2014-11-02 5:51 ` Baruch Siach
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=20141031164156.6a386482@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