Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] c-icap: avoid host library search path
Date: Thu, 21 Apr 2016 09:58:30 +0300	[thread overview]
Message-ID: <20160421065830.GP2476@tarshish> (raw)
In-Reply-To: <5717F63F.8040605@mind.be>

Hi Arnout,

On Wed, Apr 20, 2016 at 11:35:59PM +0200, Arnout Vandecappelle wrote:
> On 04/20/16 20:04, Baruch Siach wrote:
> >On Tue, Apr 19, 2016 at 09:14:57PM +0200, Thomas Petazzoni wrote:
> >>On Tue, 19 Apr 2016 21:15:44 +0300, Baruch Siach wrote:
> >>>+C_ICAP_MAKE_OPTS = exec_prefix=$(STAGING_DIR)/usr
> >>
> >>This is not correct. Setting exec_prefix to $(STAGING_DIR)/usr is
> >>wrong. Instead, can you try to remove:
> >>
> >>    -rpath @libdir@
> >>
> >>from the various Makefile.am ?
> >
> >It turns out that forcing AUTORECONF is enough to fix the problem. I'm not
> >sure why. I have only noticed that after AUTORECONF, -lz appears explicitly in
> >the link command line, whereas before libz was linked in implicitly via
> >libicapapi.so NEEDED tag. Manually running the failed link command with -lz
> >added, fixes the link as well. I guess that -lz makes the linker search in
> >sysroot before rpath, but I could not find an explanation to this behaviour in
> >the ld documentation.
> 
>  As I wrote yesterday: -rpath is used for searching for NEEDED entries, not
> for searching for -l argument. And vice versa: -L is used to search for -l
> arguments, but not for NEEDED entries.

That explains the behaviour I see, thanks. The twist here is that -rpath does 
not search for libraries that were found already as a result of -l. This 
apparently means that -L would indirectly affect the results of -rpath search.

Do you have any reference to gcc/binutils documentation on that?

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2016-04-21  6:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 18:15 [Buildroot] [PATCH 1/3] c-icap: avoid host library search path Baruch Siach
2016-04-19 18:15 ` [Buildroot] [PATCH 2/3] c-icap: bump to version 0.4.2 Baruch Siach
2016-04-19 19:16   ` Thomas Petazzoni
2016-04-20  4:28     ` Baruch Siach
2016-04-20  8:06       ` Thomas Petazzoni
2016-04-19 18:15 ` [Buildroot] [PATCH 3/3] c-icap-modules: " Baruch Siach
2016-04-19 19:14 ` [Buildroot] [PATCH 1/3] c-icap: avoid host library search path Thomas Petazzoni
2016-04-20  4:31   ` Baruch Siach
2016-04-20 18:04   ` Baruch Siach
2016-04-20 19:20     ` Thomas Petazzoni
2016-04-20 19:37       ` Baruch Siach
2016-04-20 21:35     ` Arnout Vandecappelle
2016-04-21  6:58       ` Baruch Siach [this message]
2016-04-21 13:17         ` Arnout Vandecappelle
2016-04-19 21:53 ` Arnout Vandecappelle

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=20160421065830.GP2476@tarshish \
    --to=baruch@tkos.co.il \
    --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