All of lore.kernel.org
 help / color / mirror / Atom feed
From: Malcolm Crossley <malcolm.crossley@ge.com>
To: yocto@yoctoproject.org
Subject: Re: Autobuilder issue status
Date: Wed, 03 Aug 2011 17:29:11 +0100	[thread overview]
Message-ID: <4E397757.60908@ge.com> (raw)
In-Reply-To: <201108031707.07245.paul.eggleton@linux.intel.com>

On 03/08/2011 17:07, Paul Eggleton wrote:
> Hi all,
>
> Richard requested a summary of the current issues shown up on the autobuilder,
> here it is:
>
> 1. sstate not getting cleared (autobuilder script fix needed - maybe just
> delete the whole sstate-cache dir?)
> http://autobuilder.yoctoproject.org:8010/builders/crownbay-
> noemgd/builds/27/steps/shell/logs/stdio
>
> 2. jasperforest and sugarbay need fixing for tune file changes:
> I have a first-pass patch for this, just a matter of fixing up the machine .conf
> files for these two layers.
> http://autobuilder.yoctoproject.org:8010/builders/jasperforest/builds/29/steps/shell_10/logs/stdio
>
> 3. glibc-utils PREFERRED_PROVIDER clash:
> (There's a patch merged in master for this already)
> http://autobuilder.yoctoproject.org:8010/builders/nightly-
> external/builds/57/steps/shell_6/logs/stdio
>
> 4. manifest file missing in sdk build:
> http://autobuilder.yoctoproject.org:8010/builders/nightly-external-
> toolchain/builds/52/steps/shell_7/logs/stdio
>
> 5. libXinerama missing when building gtk+
> Not sure if this is a result of previous errors?
> http://autobuilder.yoctoproject.org:8010/builders/nightly-
> internal/builds/50/steps/shell_21/logs/stdio
>
> 6. "perl isn't executable!":
> http://autobuilder.yoctoproject.org:8010/builders/nightly-
> external/builds/60/steps/shell_26/logs/stdio
I have seen possibly a similar issue: libxml-parser-perl failing to compile
I tracked it down to two problems:
a) using an sstate mirror results in the rpath that's compiled into the 
native-perl being hardcoded to the full path of whatever built the 
sstate-cache. The means the compiled in rpath is wrong on any other 
machine.

b) perl MakeMaker is using perl.real instead of the wrapper script, this 
results in the PERL5LIB variable not being passed in to perl on 
execution. This in combination with problem A means perl cannot find 
it's libraries.

I would recommend randomising the base directory for autobuilders if 
they are using an sstate mirror, in order to flush out bugs caused by 
problem A.

I cannot figure out how to fix problem B at the moment and I'll be on 
holiday soon. So I thought I'd post about this issue before I go.

>
> 7. -live images still being built:
> Beth was fixing (has fixed?) this. It did bring up an interesting issue in that
> -k makes the build look like it succeeded - have filed bug #1322 for this one.
> http://autobuilder.yoctoproject.org:8010/builders/crownbay-
> noemgd/builds/27/steps/shell_10/logs/stdio
>
> 8. meta-toolchain "/bin/sh" dependency errors:
> Richard thinks he knows what's wrong here but is unsure of the fix.
> http://autobuilder.yoctoproject.org:8010/builders/nightly-external-
> toolchain/builds/55/steps/shell_14/logs/stdio
>
> 9. aclocal .m4 file issue (bug #861)
> Richard has some potential suggestions, actual fix still needed though.
> http://autobuilder.yoctoproject.org:8010/builders/nightly-
> external/builds/60/steps/shell_14/logs/stdio
>
> 10. beagleboard libzypp failure
> Richard has a patch for part of it, would like Mark to look into the rest:
> http://bugzilla.pokylinux.org/show_bug.cgi?id=1313
>
> Cheers,
> Paul
>



  reply	other threads:[~2011-08-03 16:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 16:07 Autobuilder issue status Paul Eggleton
2011-08-03 16:29 ` Malcolm Crossley [this message]
2011-08-03 16:57 ` Flanagan, Elizabeth
2011-08-03 17:26   ` Flanagan, Elizabeth
2011-08-03 17:03 ` 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=4E397757.60908@ge.com \
    --to=malcolm.crossley@ge.com \
    --cc=yocto@yoctoproject.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 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.