Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Wrong rpath after linking with libmysqlclient
Date: Sun, 13 Dec 2015 21:13:58 +0100	[thread overview]
Message-ID: <20151213201358.GC27971@free.fr> (raw)
In-Reply-To: <566DCFFE.5070504@mind.be>

Arnout, All,

On 2015-12-13 21:07 +0100, Arnout Vandecappelle spake thusly:
>  First of all, the symptomps: build the defconfig in attachment, run with
> 
> qemu-system-arm -M nuri -kernel output/images/zImage -append \
>  "console=ttySAC1,115200" -smp 2 -serial null -serial stdio
> 
> and you'll see:
> 
> Starting php-fpm /usr/sbin/php-fpm: error while loading shared libraries:
> libmysqlclient.so.16: cannot open shared object file: No such file or directory
> 
> 
>  readelf reveals:
> 
> Library rpath: [.../host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/lib/mysql]
> 
>  i.e. rpath points to staging instead of the on-target directory.
> 
>  Indeed, in libmysqlclient.la we find:
> 
> libdir='.../host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/lib/mysql'
> 
> 
>  This happens because our 'Fixing libtool files' step makes sure that all
> absolute paths have STAGING_DIR prepended to them.
> 
> 
>  This problem will occur for any library that doesn't install in /lib or
> /usr/lib and that uses libtool.
> 
> 
>  My first idea was to install libmysqlclient.so in /usr/lib instead, but that's
> probably a great idea.

that's what Thomas and I were discussing the other day: why are those
libraries not in /usr/lib to start with? We believe this should be the
case.

> So the next idea is to skip the libdir= line when fixing
> up the libtool files. However, I'm not sure if that won't have some other
> effects (i.e. missing required link flags). But worse, it doesn't even work:
> php's libtool still converts it into
> -Wl,--rpath -Wl,.../host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/lib/mysql
> (and gives warnings that the libraries have moved.
> 
>  Any idea?
> 
>  A final option is to fix up the rpaths of all ELF files in the target after
> build. I believe Yann has a series that does exactl that, no?

The fixup I've been doing is to just get rid of rpath since it should
not be needed on the target, as we should expect all NEEDED libraries to
either be in /usr/lib or /lib .

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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-12-13 20:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-13 20:07 [Buildroot] Wrong rpath after linking with libmysqlclient Arnout Vandecappelle
2015-12-13 20:13 ` Yann E. MORIN [this message]
2015-12-13 21:22   ` 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=20151213201358.GC27971@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox