All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] How do you add to library path?
Date: Sat, 28 Apr 2012 05:44:20 -0500	[thread overview]
Message-ID: <201204280544.24157.minimod@morethan.org> (raw)
In-Reply-To: <201204280018.27254.arnout@mind.be>

On Fri April 27 2012, Arnout Vandecappelle wrote:
> On Thursday 26 April 2012 19:42:01 Grant Edwards wrote:
> > What's the right way to permanently add a directory to the search path
> > for dynamic libraries?  (Preferably at build-time, rather than at
> > run-time.)
> 
>  You could use the -rpath linker option, but that risks conflicts with
> libraries installed on the host (the linker puts rpath in front of the
> library search path, disregarding the sysroot, so if a library with the
> same name exists in that path on the host, the linker will link with that
> one instead of the cross-compiled one).
>

At a guess (untried by myself), it might be possible to use objcopy to
add/change the rpath information __after__ the build is otherwise complete.

I.E: For the case where the rpath information added is for the target's use,
rather than the build host's use.

I do not know for certain if objcopy can access or change the rpath 
information field in an object, I have never seen or read about it being done.

Mike

>  Regards,
>  Arnout
> 

  reply	other threads:[~2012-04-28 10:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 17:42 [Buildroot] How do you add to library path? Grant Edwards
2012-04-26 20:12 ` Bernhard Reutner-Fischer
2012-04-27 22:18 ` Arnout Vandecappelle
2012-04-28 10:44   ` Michael S. Zick [this message]
2012-04-28 11:15     ` Bernhard Reutner-Fischer
2012-04-28 14:13       ` Arnout Vandecappelle
2012-04-28 14:53   ` Grant Edwards

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=201204280544.24157.minimod@morethan.org \
    --to=minimod@morethan.org \
    --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.