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] host ldconfig package
Date: Fri, 7 Nov 2014 08:25:17 +0100	[thread overview]
Message-ID: <20141107082517.416a87ff@free-electrons.com> (raw)
In-Reply-To: <CAM7q1LnRANa1wFbb=5o8yuyYyJrQyU_CUDqTaNwQ7tC7905L-A@mail.gmail.com>

Dear Jeff Horn,

On Thu, 6 Nov 2014 15:42:30 -0800, Jeff Horn wrote:

> I am using buildroot for one of our i.MX6 based boards and I have it mostly
> working ( I can't get video to work ). While troubleshooting freescales
> gstreamer plugins I noticed the /etc/ld.so.cache was empty. I found in the
> buildroot makefile where ldconfig is called so I manually ran
> /sbin/ldconfig -v -r output/target and I see lots of output like this:
> 
> /sbin/ldconfig.real: /usr/lib/libGLESv2.so is for unknown machine 40.
> 
> It seems the ldconfig on my host (Ubuntu 14.04) cannot handle the tartget
> rootfs. I found a post from a year ago with the same issue but I did not
> see any resolution.
> 
> So, I looked at my current Yocto build and I discovered Yocto builds a
> native hacked version of ldconfig and that is what gets called for the
> target rootfs. So, I copied that binary over and modified buildroots
> Makefile to call that instead and the cache is now populated correctly.
> 
> With that all working I created a buildroot host ldconfig package based on
> the Yocto code ( I'm using BR2_EXTERNAL) and using that the ld.so.cache
> gets populated. I still had to modify the buildoort Makfile to look for the
> newly installed host ldconfig.
> 
> I guess my question is are others having any issues with image finalization
> and ldconfig?

Yes, this is a known issue. I remember we discussed it last month at
the Buildroot Developers meeting. At the time, our feeling was that we
would completely get rid of the ldconfig handling, and live without a
ld.so.cache, since ld.so.cache is not strictly needed for runtime
execution. The problem is indeed as you've seen, is that a cross
ldconfig is not something that exists upstream in glibc, and only
hacked versions are available. So either we decide to package such
"hacked" versions, or we give up on having a ld.so.cache entirely.

> On another note I see others are working on the fsl-gst-plugins and I can
> help test that as I REALLY want to get a working image out of buildroot.

I'm adding in Cc some i.MX6 folks from the Buildroot community: Gary,
J?r?me and Luca.

Best regards,

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

  reply	other threads:[~2014-11-07  7:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 23:42 [Buildroot] host ldconfig package Jeff Horn
2014-11-07  7:25 ` Thomas Petazzoni [this message]
2014-11-07 16:35 ` Jérôme Pouiller
2014-11-07 17:43   ` Jeff Horn
2014-11-08 21:56     ` Gary Bisson
2014-11-10  9:41       ` Jérôme Pouiller
2014-11-11  0:04       ` Jeff Horn
2014-11-11 21:26         ` Jeff Horn

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=20141107082517.416a87ff@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