From: Mike Looijmans <mike.looijmans@topic.nl>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][PATCH] phytool: Add recipe
Date: Wed, 28 Sep 2016 09:55:25 +0200 [thread overview]
Message-ID: <57EB776D.8070604@topic.nl> (raw)
In-Reply-To: <57EB71B3.6060803@topic.nl>
On 28-09-16 09:30, Mike Looijmans wrote:
> On 26-09-16 22:34, Martin Jansa wrote:
>> 2 more issues:
>>
>> WARNING: phytool-1.0.1-r0 do_populate_lic: Could not copy license file
>> phytool/1.0.1-r0/git/COPYING to
>> phytool/1.0.1-r0/license-destdir/phytool/COPYING: [Errno 2] No such
>> file or directory: 'phytool/1.0.1-r0/git/COPYING'
>> ERROR: phytool-1.0.1-r0 do_populate_lic: QA Issue: phytool:
>> LIC_FILES_CHKSUM points to an invalid file:
>> phytool/1.0.1-r0/git/COPYING [license-checksum]
>> NOTE: recipe phytool-1.0.1-r0: task do_populate_lic: Succeeded
>> ...
>
> Weird, it didn't barf on that on my system until I cleaned it and started
> over. Ah well, I;ll send a v2 which fixes it.
>
>> NOTE: recipe phytool-1.0.1-r0: task do_package_qa: Started
>> ERROR: phytool-1.0.1-r0 do_package_qa: QA Issue: No GNU_HASH in the
>> elf binary: 'phytool/1.0.1-r0/packages-split/phytool/usr/bin/phytool'
>> [ldflags]
>> ERROR: phytool-1.0.1-r0 do_package_qa: QA Issue: No GNU_HASH in the
>> elf binary: 'phytool/1.0.1-r0/packages-split/phytool/usr/bin/phytool'
>> [ldflags]
>> ERROR: phytool-1.0.1-r0 do_package_qa: QA run found fatal errors.
>> Please consider fixing them.
>> ERROR: phytool-1.0.1-r0 do_package_qa: Function failed: do_package_qa
>
> I have no clue what that means. I also have no clue what I'm supposed to do
> about it. And on my build it was only a warning.
A bit of experimentation revealed that apparently this is OE complaining that
$LDFLAGS didn't get passed to the linker. Created a patch to solve that and
upstream it.
It would be helpful if the message wasn't so cryptic.
Kind regards,
Mike Looijmans
System Expert
TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
next prev parent reply other threads:[~2016-09-28 8:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 12:33 [meta-networking][PATCH] phytool: Add recipe Mike Looijmans
2016-09-23 18:33 ` Khem Raj
2016-09-24 15:01 ` Mike Looijmans
2016-09-26 7:31 ` Khem Raj
2016-09-26 20:34 ` Martin Jansa
2016-09-28 7:30 ` Mike Looijmans
2016-09-28 7:55 ` Mike Looijmans [this message]
2016-10-05 9:34 ` [meta-networking][PATCH v2] " Mike Looijmans
2016-10-05 15:38 ` Khem Raj
2016-10-05 16:32 ` Martin Jansa
2016-10-06 5:54 ` Mike Looijmans
2016-09-28 7:53 ` [PATCH " Mike Looijmans
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=57EB776D.8070604@topic.nl \
--to=mike.looijmans@topic.nl \
--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