Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: niqingliang@insigma.com.cn,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: gconf build error
Date: Fri, 23 Mar 2012 09:30:11 +0000	[thread overview]
Message-ID: <1332495011.9740.384.camel@ted> (raw)
In-Reply-To: <1332491527.11882.40.camel@localhost.localdomain>

On Fri, 2012-03-23 at 16:32 +0800, Ni Qingliang wrote:
> Hello,
> 
> I have made some progress after struggled a few days on it. found that
> the reason is located in the 'ld'.
> following is my investigation (focused on the IMPLICIT depended
> library):
> 
> 1. call ld with sysroot and rpath
> $ld --sysroot=/media/pangu/lsbt/tmp/sysroots/qemux86-64 ...
> -rpath /usr/lib/../lib
> 
> then it will find the lib needed in the host's rootfs, that will result
> error.
> 
> 2. call ld with sysroot and without rpath
> $ld --sysroot=/media/pangu/lsbt/tmp/sysroots/qemux86-64 ... 
> 
> then it will find the lib needed in the directory sysroot arg specified.
> that is expected.
> 
> I found that using the --verbose argument. Is the behaviour expected? or
> a bug? 

That behaviour is expected. You should not be passing rpath /usr/lib
options to ld.

Cheers,

Richard




  reply	other threads:[~2012-03-23  9:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15  8:18 LSB support? Ni Qingliang
2012-03-15 16:25 ` Mark Hatle
2012-03-16  2:38   ` Ni Qingliang
2012-03-16  5:18   ` Ni Qingliang
2012-03-16 15:36     ` Mark Hatle
2012-03-19  1:47       ` Ni Qingliang
2012-03-19  6:33         ` Ni Qingliang
2012-03-19 16:07         ` Mark Hatle
2012-03-20  2:56         ` Ni Qingliang
2012-03-20  9:20       ` Ni Qingliang
2012-03-21  8:45         ` gconf build error Ni Qingliang
2012-03-23  8:32           ` Ni Qingliang
2012-03-23  9:30             ` Richard Purdie [this message]
2012-03-23  9:40             ` Ni Qingliang

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=1332495011.9740.384.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=niqingliang@insigma.com.cn \
    --cc=openembedded-core@lists.openembedded.org \
    /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