From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Allowing user to run ldconfig in post-build script
Date: Thu, 16 Jun 2016 22:34:03 +0200 [thread overview]
Message-ID: <20160616203403.GJ3665@free.fr> (raw)
In-Reply-To: <20160616222854.6b20890a@free-electrons.com>
Thomas, ?ric, All,
On 2016-06-16 22:28 +0200, Thomas Petazzoni spake thusly:
> On Thu, 16 Jun 2016 21:45:22 +0200, Eric Le Bihan wrote:
> > > > Not being able to run ldconfig and generate the ld.so cache has two
> > > > drawbacks:
[--SNIP--]
> > uclibc-ng also provides ldconfig, which behaves like the glibc version
> > (see ldso/man/ldconfig.8 in the source tree).
>
> OK. But IIRC, the ld.so.cache functionality in uClibc-ng is optional,
> and I'm not sure we have it enabled by default.
>
> The uClibc-ng ld.so.cache format would be fully compatible with
> the one used in glibc ?
AFAICS, yes. Their ldocnfig code looks suspiciously like the glibc one.
> > > Another thing that bothers me is why it is not possible to have a
> > > cross-compilation aware ldconfig. This would really be much, much
> > > nicer than running ldconfig under qemu.
> >
> > Yocto provides a recipe named ldconfig-native_2.12.1.bb [1], which
> > contains a verbatim copy of the ldconfig source code from glibc, and a
> > truck load of patches. It looks a bit hairy...
> >
> > [1] http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/glibc/ldconfig-native_2.12.1.bb
>
> Yes, I know they are doing this with a shitload of patches. Maybe we
> should host a project on github for a cross-compilation capable
> ldconfig, and then offer the Yocto people to use it?
Meh... ;-]
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-06-16 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1722059483.342813959.1466082436418.JavaMail.root@zimbra32-e6.priv.proxad.net>
2016-06-16 13:12 ` [Buildroot] Allowing user to run ldconfig in post-build script Eric Le Bihan
2016-06-16 13:37 ` Thomas Petazzoni
2016-06-16 19:45 ` Eric Le Bihan
2016-06-16 20:28 ` Thomas Petazzoni
2016-06-16 20:34 ` Yann E. MORIN [this message]
2016-06-16 21:15 ` Eric Le Bihan
2016-06-23 22:22 ` Arnout Vandecappelle
2016-06-16 19:53 ` Yann E. MORIN
2016-06-16 20:34 ` Thomas Petazzoni
2016-06-16 21:32 ` Eric Le Bihan
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=20160616203403.GJ3665@free.fr \
--to=yann.morin.1998@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.