From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Lewis, Nick" <nick.lewis@usa.g4s.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Help with redundant RPATH /usr/lib
Date: Tue, 23 Apr 2013 12:46:07 +0100 [thread overview]
Message-ID: <1366717567.23738.55.camel@ted> (raw)
In-Reply-To: <AAE0766F5AF36B46BAB7E0EFB927320630E4A540BF@GBTWK10E001.Technology.local>
On Tue, 2013-04-23 at 12:10 +0100, Lewis, Nick wrote:
> >If that isn't the reason, its likely you're doing something custom to the linking command in configure.ac or Makefile.am and breaking it.
>
> Richard
>
> I have added a patch to the recipe that appears to fix the problem. Is this a reasonable approach to the issue?
>
> $ cat sources/meta-nick/recipes-nick/xar/xar-1.5.2/xar-rpath.patch
> --- a/src/Makefile.inc.in 2013-04-17 18:03:12.704735379 -0700
> +++ b/src/Makefile.inc.in 2013-04-17 17:52:41.684668367 -0700
> @@ -54,7 +54,11 @@
> @objroot@src/i% : @objroot@src/%.o $(LIBXAR)
> @mkdir -p $(@D)
> ifneq ($(words "" @RPATH@), 1)
> + ifeq (/usr/lib, $(LIBDIR))
> + $(CC) $(CFLAGS) -o $@ $< $(LDFLAGS) $(LIBXAR) @LIBS@
> + else
> $(CC) $(CFLAGS) -o $@ $< @RPATH@$(LIBDIR) $(LDFLAGS) $(LIBXAR) @LIBS@
> + endif
> else
> $(CC) $(CFLAGS) -o $@ $< $(LDFLAGS) $(LIBXAR) @LIBS@
> endif
Its certainly better, yes. libdir might not always equal /usr/lib of
course, in libtool it compared against the system search path list but I
think you've at least tracked down the cause of your problem.
Cheers,
Richard
next prev parent reply other threads:[~2013-04-23 11:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 13:32 Help with redundant RPATH /usr/lib Lewis, Nick
2013-04-22 13:51 ` Fabio Estevam
2013-04-22 14:34 ` Richard Purdie
2013-04-22 15:48 ` Lewis, Nick
2013-04-23 11:10 ` Lewis, Nick
2013-04-23 11:46 ` Richard Purdie [this message]
2013-04-23 13:13 ` Lewis, Nick
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=1366717567.23738.55.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=meta-freescale@yoctoproject.org \
--cc=nick.lewis@usa.g4s.com \
/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.