From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: meta-freescale <meta-freescale@yoctoproject.org>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: meta-fsl-arm build failure
Date: Fri, 11 Jul 2014 09:06:22 +0100 [thread overview]
Message-ID: <1405065982.15985.81.camel@ted> (raw)
amd-gpu-x11-bin/amd-gpu-mx51.inc contains:
# FIXME: All binaries lack GNU_HASH in elf binary but as we don't have
# the source we cannot fix it. Disable the insane check for now.
python populate_packages_prepend() {
for p in d.getVar('PACKAGES', True).split():
d.setVar("INSANE_SKIP_%s" % p, "ldflags")
}
and with the recent change that merged to make package QA a separate
task, this no longer works. I'd suggest you change this to:
python {
for p in d.getVar('PACKAGES', True).split():
d.setVar("INSANE_SKIP_%s" % p, "ldflags")
}
which should fix the issue. Doing that as a populate_packages prepend
wasn't the nicest of things to be doing in the first place.
Cheers,
Richard
next reply other threads:[~2014-07-11 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 8:06 Richard Purdie [this message]
2014-07-11 12:06 ` meta-fsl-arm build failure Otavio Salvador
-- strict thread matches above, loose matches on Subject: below --
2014-03-17 9:30 Richard Purdie
2014-03-17 23:14 ` Otavio Salvador
2014-03-17 23:21 ` 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=1405065982.15985.81.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.