Re: [meta-networking][PATCH] phytool: Add recipe

[Mike Looijmans <mike.looijmans@topic.nl>]

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.


>
>
> On Mon, Sep 26, 2016 at 9:31 AM, Khem Raj <raj.khem@gmail.com> wrote:
>
>> On Sat, Sep 24, 2016 at 8:01 AM, Mike Looijmans <mike.looijmans@topic.nl>
>> wrote:
>>> On 23-09-16 20:33, Khem Raj wrote:
>>>>
>>>> On Fri, Sep 23, 2016 at 5:33 AM, Mike Looijmans <
>> mike.looijmans@topic.nl>
>>>> wrote:
>>>>>
>>>>> A nice tool to directly read, write and interpret ethernet PHY data.
>>>>> Very useful when debugging PHY or MDIO problems, which ethtool does
>>>>> not do.
>>>>>
>>>>> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
>>>>> ---
>>>>>    meta-networking/recipes-support/phytool/phytool.bb | 14
>> ++++++++++++++
>>>>>    1 file changed, 14 insertions(+)
>>>>>    create mode 100644 meta-networking/recipes-support/phytool/
>> phytool.bb
>>>>>
>>>>> diff --git a/meta-networking/recipes-support/phytool/phytool.bb
>>>>> b/meta-networking/recipes-support/phytool/phytool.bb
>>>>> new file mode 100644
>>>>> index 0000000..9d541b7
>>>>> --- /dev/null
>>>>> +++ b/meta-networking/recipes-support/phytool/phytool.bb
>>>>> @@ -0,0 +1,14 @@
>>>>> +SUMMARY = "PHY interface tool for Linux"
>>>>> +LICENSE = "GPLv2"
>>>>> +LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae1
>> 9f"
>>>>> +
>>>>> +PV = "1.0.1"
>>>>> +SRCREV = "1a3ea62a218206e9faf3b27fb5d01c85692024c8"
>>>>> +SRC_URI = "git://github.com/wkz/phytool.git"
>>>>> +
>>>>> +S = "${WORKDIR}/git"
>>>>> +
>>>>> +do_install() {
>>>>> +       install -d ${D}${prefix}/bin
>>>>
>>>>
>>>> perhaps use base_bindir here
>>>
>>>
>>> The makefile installs to $PREFIX/bin so I deliberately put the same
>> folder
>>> in the recipe (the makefile doesn't create the directory). If anyone
>> changes
>>> $bindir the install will fail.
>>
>> I see the logic,  if you dont want to use bitbake variables then perhaps
>> its
>> good to add a comment to explain why it was not done
>>
>>>
>>>>
>>>>> +       oe_runmake 'DESTDIR=${D}' 'PREFIX=${prefix}' install
>>>>> +}
>>>>> --
>>>>> 1.9.1
>>>>>
>>>>> --
>>>>> 

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





_______________________________________________
>>>>> Openembedded-devel mailing list
>>>>> Openembedded-devel@lists.openembedded.org
>>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>>
>>>
>>>
>>> --
>>> Mike Looijmans
>>>
>>> --
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>