From: "Mark Gollahon" <golly@stellarwerx.com>
To: openembedded-devel@lists.openembedded.org
Subject: QA issue with *.PC file
Date: Thu, 22 Feb 2007 09:49:29 -0500 (EST) [thread overview]
Message-ID: <1172155769.7346@gatekeeper.stellarwerx.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
Ok, I know I'm going to get heckled on this one. However, has the *.pc sanity check been fixed for later versions of udev when building angstrom?
Regards,
-Mark Gollahon
===========================================================
OE Build Configuration:
BB_VERSION = "1.6.6"
OE_REVISION = "b3d0613a356ef781ed84bdb1cd373059e4210cdd"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "spitz"
DISTRO = "angstrom"
DISTRO_VERSION = "test-20070222"
TARGET_FPU = "soft"
NOTE: preferred version 2.5 of glibc not available
NOTE: package udev-092: started
NOTE: package udev-092-r15: task do_qa_staging: started
NOTE: QA checking staging
ERROR: QA issue: libvolume_id.pc failed sanity test (reference to /usr/include or workdir)
ERROR: QA staging was broken by the package built above
ERROR: Error in executing: /var/tmp/OpenEmbedded/org.openembedded.dev/packages/udev/udev_092.bb
ERROR: Exception:exceptions.SystemExit Message:1
ERROR: Printing the environment of the function
reply other threads:[~2007-02-22 14:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1172155769.7346@gatekeeper.stellarwerx.com \
--to=golly@stellarwerx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox