From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Release-2011.03 - package acl contains bad RPATH
Date: Fri, 18 Feb 2011 10:49:19 -0700 [thread overview]
Message-ID: <4D5EB11F.5040007@mentor.com> (raw)
In-Reply-To: <4D5EA4CA.7090205@dresearch.de>
On 02/18/2011 09:56 AM, Steffen Sledz wrote:
> First negativ test result :(
>
> NOTE: Running task 963 of 1217 (ID: 668, /var/lib/jenkins/jobs/OE-testing/workspace/openembedded/recipes/udev/acl_2.2.49.bb, do_package)
> NOTE: package acl-2.2.49-r3: task do_package: Started
> ERROR: QA Issue with acl: package acl contains bad RPATH /var/lib/jenkins/jobs/OE-testing/workspace/tmp/sysroots/armv5te-angstrom-linux-gnueabi/usr/lib in file /var/lib/jenkins/jobs/OE-testing/workspace/tmp/work/armv5te-angstrom-linux-gnueabi/acl-2.2.49-r3/packages-split/acl/usr/lib/libacl.so.1.1.0
> ERROR: QA Issue with acl: package acl contains bad RPATH /var/lib/jenkins/jobs/OE-testing/workspace/tmp/sysroots/armv5te-angstrom-linux-gnueabi/usr/lib in file /var/lib/jenkins/jobs/OE-testing/workspace/tmp/work/armv5te-angstrom-linux-gnueabi/acl-2.2.49-r3/packages-split/acl/usr/lib/libacl.so.1
> ERROR: Task 668 (/var/lib/jenkins/jobs/OE-testing/workspace/openembedded/recipes/udev/acl_2.2.49.bb, do_package) failed with 256
> FATAL: QA run found fatal errors. Please consider fixing them.
Yeap. My current goal is to hammer out many more of the RPATH issues
that still exist after
http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?h=trini/simplify-target-flags
and update the release branch again Tuesday.
--
Tom Rini
Mentor Graphics Corporation
prev parent reply other threads:[~2011-02-18 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 16:56 Release-2011.03 - package acl contains bad RPATH Steffen Sledz
2011-02-18 17:49 ` Tom Rini [this message]
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=4D5EB11F.5040007@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@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 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.