Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: do_populate_sysroot: Function failed: relocatable_binaries_preprocess
Date: Mon, 23 Jan 2017 10:48:26 -0600	[thread overview]
Message-ID: <25726cb2-3125-5ad5-e69a-9ae4269fed53@windriver.com> (raw)
In-Reply-To: <20170123164454.GT29778@windriver.com>

On 1/23/17 10:44 AM, Paul Gortmaker wrote:
> After updating this morning (everything on master, re-using the existing
> build dir that was built OK within the last 48h) I saw this:
> 
> ERROR: pseudo-native-1.8.1-r0 do_populate_sysroot: pseudo-native: chrpath command failed with exit code 7:
> b'/home/paul/poky/build/tmp/work/x86_64-linux/pseudo-native/1.8.1-r0/sysroot-destdir/home/paul/poky/build/tmp/work/x86_64-linux/pseudo-native/1.8.1-r0/recipe-sysroot-native/usr/bin/pseudodb:
> RPATH=/home/paul/poky/build/tmp/sysroots/x86_64-linux/usr/lib:/home/paul/poky/build/tmp/sysroots/x86_64-linux/lib\n'b"new
> rpath
> '$ORIGIN/../../../../../../../sysroots/x86_64-linux/usr/lib:$ORIGIN/../../../../../../../sysroots/x86_64-linux/lib' too large; maximum length 107\n"
> ERROR: pseudo-native-1.8.1-r0 do_populate_sysroot: Function failed: relocatable_binaries_preprocess
> ERROR: Logfile of failure stored in: /home/paul/poky/build/tmp/work/x86_64-linux/pseudo-native/1.8.1-r0/temp/log.do_populate_sysroot.11

Looking at it, the error from chrpath is easy to explain.  The original RPATH
value is shorted then the new RPATH value that was calculated.

i.e.:
/home/paul/poky/build/tmp/sysroots/x86_64-linux/usr/lib

vs

$ORIGIN/../../../../../../../sysroots/x86_64-linux/usr/lib

So the system errors because it would overflow the buffer inside of the ELF object.

What is strange is this issue is new.  It means something has changed in the
origin processing of native packages over the weekend.

I'm wondering if this has something to do with the new recipe specific sysroot.

It should hopefully be easy to _workaround_ this issue, by having the build
directory in a deeper path  (something with more characters in it.)

But this is a big enough program we're going to have to figure out how to solve it.

--Mark

> I did a cleansstate on that and then it was fine but then openssl died
> in the same way:
> 
> ERROR: openssl-native-1.0.2j-r0 do_populate_sysroot: openssl-native: chrpath command failed with exit code 7:
> b'/home/paul/poky/build/tmp/work/x86_64-linux/openssl-native/1.0.2j-r0/sysroot-destdir/home/paul/poky/build/tmp/work/x86_64-linux/openssl-native/1.0.2j-r0/recipe-sysroot-native/usr/lib/libssl.so.1.0.0: RPATH=/home/paul/poky/build/tmp/sysroots/x86_64-linux/usr/lib:/home/paul/poky/build/tmp/sysroots/x86_64-linux/lib\n'b"new rpath '$ORIGIN/../../../../../../../sysroots/x86_64-linux/usr/lib:$ORIGIN/../../../../../../../sysroots/x86_64-linux/lib' too large; maximum length 107\n"
> ERROR: openssl-native-1.0.2j-r0 do_populate_sysroot: Function failed: relocatable_binaries_preprocess
> ERROR: Logfile of failure stored in: /home/paul/poky/build/tmp/work/x86_64-linux/openssl-native/1.0.2j-r0/temp/log.do_populate_sysroot.7182
> ERROR: Task (virtual:native:/home/paul/poky/meta/recipes-connectivity/openssl/openssl_1.0.2j.bb:do_populate_sysroot) failed with exit code '1'
> 
> I mentioned it to Mark and he suggested I should mention it here.
> 
> P.
> 
> 



  reply	other threads:[~2017-01-23 16:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 16:44 do_populate_sysroot: Function failed: relocatable_binaries_preprocess Paul Gortmaker
2017-01-23 16:48 ` Mark Hatle [this message]
2017-01-23 17:53 ` Richard Purdie

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=25726cb2-3125-5ad5-e69a-9ae4269fed53@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.gortmaker@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox