From: David Huggins-Daines <dhuggins@cs.cmu.edu>
To: openembedded-devel@openembedded.org
Subject: Canadian Cross building broken due to PN in pkginfo files
Date: Wed, 15 Apr 2009 12:35:30 -0400 [thread overview]
Message-ID: <49E60CD2.2080806@cs.cmu.edu> (raw)
This issue:
http://thread.gmane.org/gmane.comp.handhelds.openembedded/22376/focus=22556
also seems to affect building gcc-canadian-sdk - it leads to a "lockfile
path does not exist!" error where it's trying to create a lockfile in
the work directory for gcc-4.2.4-r3.
The problem happens here, in read_subpackage_metadata():
for pkg in bb.data.getVar('PACKAGES', d, 1).split():
sdata = read_subpkgdata(pkg, d)
for key in sdata.keys():
bb.data.setVar(key, sdata[key], d)
The problem is that ${PN} is defined in the subpackage's pkginfo file,
so it overwrites the definition from the main package. The last
subpackage defines PN="gcc", so that's where the packaging stage tries
to put the lockfile.
The original fix suggested in that thread seems to work well:
git revert -n 1af5030de05a1e65d1de734f7675ffc22c8318fc
I'm not sure what other packages or tasks this change might be affecting.
reply other threads:[~2009-04-15 16:41 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=49E60CD2.2080806@cs.cmu.edu \
--to=dhuggins@cs.cmu.edu \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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