* Building test code? @ 2021-03-15 23:11 jchludzinski 2021-03-15 23:54 ` [yocto] " akuster 0 siblings, 1 reply; 10+ messages in thread From: jchludzinski @ 2021-03-15 23:11 UTC (permalink / raw) To: Yocto [-- Attachment #1: Type: text/plain, Size: 321 bytes --] I got a piece of code from github: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/spi/spidev_test.c I'd like to add it somewhere under _tools/testing_ and build it there. Not sure if this is appropriate? If so, how do I go about this? If not, what's the best way to build this? [-- Attachment #2: Type: text/html, Size: 827 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [yocto] Building test code? 2021-03-15 23:11 Building test code? jchludzinski @ 2021-03-15 23:54 ` akuster 2021-03-16 7:07 ` jchludzinski 0 siblings, 1 reply; 10+ messages in thread From: akuster @ 2021-03-15 23:54 UTC (permalink / raw) To: jchludzinski, Yocto On 3/15/21 4:11 PM, jchludzinski via lists.yoctoproject.org wrote: > I got a piece of code from github: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/spi/spidev_test.c > > I'd like to add it somewhere under /*tools/testing*/ and build it there. > > Not sure if this is appropriate? If so, how do I go about this? > > If not, what's the best way to build this? Is this what you are looking for? https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-kernel/spidev-test/spidev-test.bb -armin > > > ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [yocto] Building test code? 2021-03-15 23:54 ` [yocto] " akuster @ 2021-03-16 7:07 ` jchludzinski 2021-03-16 9:49 ` Nicolas Dechesne 0 siblings, 1 reply; 10+ messages in thread From: jchludzinski @ 2021-03-16 7:07 UTC (permalink / raw) To: akuster; +Cc: Yocto [-- Attachment #1: Type: text/plain, Size: 852 bytes --] It certainly appears to be BUT I'm not certain what I'm looking at? What is _meta-openembedded_? Is it a GIT repo that can be cloned and built? How do I use this to build _spidev-test_? ---John On 2021-03-15 19:54, akuster wrote: > On 3/15/21 4:11 PM, jchludzinski via lists.yoctoproject.org wrote: > >> I got a piece of code from github: >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/spi/spidev_test.c >> >> I'd like to add it somewhere under /*tools/testing*/ and build it there. >> >> Not sure if this is appropriate? If so, how do I go about this? >> >> If not, what's the best way to build this? > > Is this what you are looking for? > https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-kernel/spidev-test/spidev-test.bb > > -armin > >> > > [-- Attachment #2: Type: text/html, Size: 1958 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [yocto] Building test code? 2021-03-16 7:07 ` jchludzinski @ 2021-03-16 9:49 ` Nicolas Dechesne 2021-03-16 9:58 ` Josef Holzmayr 0 siblings, 1 reply; 10+ messages in thread From: Nicolas Dechesne @ 2021-03-16 9:49 UTC (permalink / raw) To: jchludzinski; +Cc: akuster, Yocto On Tue, Mar 16, 2021 at 8:07 AM jchludzinski via lists.yoctoproject.org <jchludzinski=vivaldi.net@lists.yoctoproject.org> wrote: > > It certainly appears to be BUT I'm not certain what I'm looking at? > > What is meta-openembedded? > > Is it a GIT repo that can be cloned and built? Short answer is yes. The whole Yocto Project / Open Embedded concept is based around 'layers. A layer is a repository that contains recipes (and/or machine/distro, ..). The Yocto Project releases include a couple of common/core layers, but there are plenty of layers out there which can be used I am sure there are quite a bit of documentation on this topic, but perhaps you might want to start with: https://docs.yoctoproject.org/overview-manual/yp-intro.html#the-yocto-project-layer-model > > > > How do I use this to build spidev-test? > > > ---John > > > On 2021-03-15 19:54, akuster wrote: > > On 3/15/21 4:11 PM, jchludzinski via lists.yoctoproject.org wrote: > > I got a piece of code from github: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/spi/spidev_test.c > > I'd like to add it somewhere under /*tools/testing*/ and build it there. > > Not sure if this is appropriate? If so, how do I go about this? > > If not, what's the best way to build this? > > > Is this what you are looking for? > https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-kernel/spidev-test/spidev-test.bb > > -armin > > > > > > > > > > ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [yocto] Building test code? 2021-03-16 9:49 ` Nicolas Dechesne @ 2021-03-16 9:58 ` Josef Holzmayr 2021-03-16 14:53 ` jchludzinski [not found] ` <166CDA589776C94C.8652@lists.yoctoproject.org> 0 siblings, 2 replies; 10+ messages in thread From: Josef Holzmayr @ 2021-03-16 9:58 UTC (permalink / raw) To: Nicolas Dechesne; +Cc: jchludzinski, akuster, Yocto Am Di., 16. März 2021 um 10:49 Uhr schrieb Nicolas Dechesne <nicolas.dechesne@linaro.org>: > > On Tue, Mar 16, 2021 at 8:07 AM jchludzinski via > lists.yoctoproject.org > <jchludzinski=vivaldi.net@lists.yoctoproject.org> wrote: > > > > It certainly appears to be BUT I'm not certain what I'm looking at? > > > > What is meta-openembedded? > > > > Is it a GIT repo that can be cloned and built? > > Short answer is yes. The whole Yocto Project / Open Embedded concept > is based around 'layers. A layer is a repository that contains recipes > (and/or machine/distro, ..). The Yocto Project releases include a > couple of common/core layers, but there are plenty of layers out there > which can be used > I am sure there are quite a bit of documentation on this topic, but > perhaps you might want to start with: > https://docs.yoctoproject.org/overview-manual/yp-intro.html#the-yocto-project-layer-model Or grab a beer and start bingewatching https://www.youtube.com/playlist?list=PLD4M5FoHz-TxMfBFrDKfIS_GLY25Qsfyj </SCNR> > > > > > > > > > > How do I use this to build spidev-test? > > > > > > ---John > > > > > > On 2021-03-15 19:54, akuster wrote: > > > > On 3/15/21 4:11 PM, jchludzinski via lists.yoctoproject.org wrote: > > > > I got a piece of code from github: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/spi/spidev_test.c > > > > I'd like to add it somewhere under /*tools/testing*/ and build it there. > > > > Not sure if this is appropriate? If so, how do I go about this? > > > > If not, what's the best way to build this? > > > > > > Is this what you are looking for? > > https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-kernel/spidev-test/spidev-test.bb > > > > -armin > > > > > > > > > > > > > > > > > > > > > > > ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [yocto] Building test code? 2021-03-16 9:58 ` Josef Holzmayr @ 2021-03-16 14:53 ` jchludzinski [not found] ` <166CDA589776C94C.8652@lists.yoctoproject.org> 1 sibling, 0 replies; 10+ messages in thread From: jchludzinski @ 2021-03-16 14:53 UTC (permalink / raw) To: Josef Holzmayr; +Cc: Nicolas Dechesne, akuster, Yocto Well, because time is of the essence, could you give me a little assist here and explain how I might build spidev-test using OpenEmbedded? THANKS for your help! ---John On 2021-03-16 05:58, Josef Holzmayr wrote: > Am Di., 16. März 2021 um 10:49 Uhr schrieb Nicolas Dechesne > <nicolas.dechesne@linaro.org>: >> >> On Tue, Mar 16, 2021 at 8:07 AM jchludzinski via >> lists.yoctoproject.org >> <jchludzinski=vivaldi.net@lists.yoctoproject.org> wrote: >> > >> > It certainly appears to be BUT I'm not certain what I'm looking at? >> > >> > What is meta-openembedded? >> > >> > Is it a GIT repo that can be cloned and built? >> >> Short answer is yes. The whole Yocto Project / Open Embedded concept >> is based around 'layers. A layer is a repository that contains recipes >> (and/or machine/distro, ..). The Yocto Project releases include a >> couple of common/core layers, but there are plenty of layers out there >> which can be used >> I am sure there are quite a bit of documentation on this topic, but >> perhaps you might want to start with: >> https://docs.yoctoproject.org/overview-manual/yp-intro.html#the-yocto-project-layer-model > > Or grab a beer and start bingewatching > https://www.youtube.com/playlist?list=PLD4M5FoHz-TxMfBFrDKfIS_GLY25Qsfyj > > </SCNR> > >> >> >> > >> > >> > >> > How do I use this to build spidev-test? >> > >> > >> > ---John >> > >> > >> > On 2021-03-15 19:54, akuster wrote: >> > >> > On 3/15/21 4:11 PM, jchludzinski via lists.yoctoproject.org wrote: >> > >> > I got a piece of code from github: >> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/spi/spidev_test.c >> > >> > I'd like to add it somewhere under /*tools/testing*/ and build it there. >> > >> > Not sure if this is appropriate? If so, how do I go about this? >> > >> > If not, what's the best way to build this? >> > >> > >> > Is this what you are looking for? >> > https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-kernel/spidev-test/spidev-test.bb >> > >> > -armin >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> >> >> > > > ^ permalink raw reply [flat|nested] 10+ messages in thread
[parent not found: <166CDA589776C94C.8652@lists.yoctoproject.org>]
* Re: [yocto] Building test code? [not found] ` <166CDA589776C94C.8652@lists.yoctoproject.org> @ 2021-03-16 15:50 ` jchludzinski [not found] ` <166CDD724205027D.27789@lists.yoctoproject.org> 1 sibling, 0 replies; 10+ messages in thread From: jchludzinski @ 2021-03-16 15:50 UTC (permalink / raw) To: jchludzinski; +Cc: Josef Holzmayr, Nicolas Dechesne, akuster, Yocto I'm 'bitbaking' now. On 2021-03-16 10:53, jchludzinski via lists.yoctoproject.org wrote: > Well, because time is of the essence, could you give me a little > assist here and explain how I might build spidev-test using > OpenEmbedded? > > THANKS for your help! > ---John > > > On 2021-03-16 05:58, Josef Holzmayr wrote: >> Am Di., 16. März 2021 um 10:49 Uhr schrieb Nicolas Dechesne >> <nicolas.dechesne@linaro.org>: >>> >>> On Tue, Mar 16, 2021 at 8:07 AM jchludzinski via >>> lists.yoctoproject.org >>> <jchludzinski=vivaldi.net@lists.yoctoproject.org> wrote: >>> > >>> > It certainly appears to be BUT I'm not certain what I'm looking at? >>> > >>> > What is meta-openembedded? >>> > >>> > Is it a GIT repo that can be cloned and built? >>> >>> Short answer is yes. The whole Yocto Project / Open Embedded concept >>> is based around 'layers. A layer is a repository that contains >>> recipes >>> (and/or machine/distro, ..). The Yocto Project releases include a >>> couple of common/core layers, but there are plenty of layers out >>> there >>> which can be used >>> I am sure there are quite a bit of documentation on this topic, but >>> perhaps you might want to start with: >>> https://docs.yoctoproject.org/overview-manual/yp-intro.html#the-yocto-project-layer-model >> >> Or grab a beer and start bingewatching >> https://www.youtube.com/playlist?list=PLD4M5FoHz-TxMfBFrDKfIS_GLY25Qsfyj >> >> </SCNR> >> >>> >>> >>> > >>> > >>> > >>> > How do I use this to build spidev-test? >>> > >>> > >>> > ---John >>> > >>> > >>> > On 2021-03-15 19:54, akuster wrote: >>> > >>> > On 3/15/21 4:11 PM, jchludzinski via lists.yoctoproject.org wrote: >>> > >>> > I got a piece of code from github: >>> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/spi/spidev_test.c >>> > >>> > I'd like to add it somewhere under /*tools/testing*/ and build it there. >>> > >>> > Not sure if this is appropriate? If so, how do I go about this? >>> > >>> > If not, what's the best way to build this? >>> > >>> > >>> > Is this what you are looking for? >>> > https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-kernel/spidev-test/spidev-test.bb >>> > >>> > -armin >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> >>> >>> >> >> >> > > > ^ permalink raw reply [flat|nested] 10+ messages in thread
[parent not found: <166CDD724205027D.27789@lists.yoctoproject.org>]
* Re: [yocto] Building test code? [not found] ` <166CDD724205027D.27789@lists.yoctoproject.org> @ 2021-03-16 18:39 ` jchludzinski 2021-03-16 18:43 ` Robert P. J. Day 0 siblings, 1 reply; 10+ messages in thread From: jchludzinski @ 2021-03-16 18:39 UTC (permalink / raw) To: jchludzinski Cc: Josef Holzmayr, Nicolas Dechesne, akuster, Yocto, jchludzinski via lists.yoctoproject.org [-- Attachment #1: Type: text/plain, Size: 4622 bytes --] I tried to build spidev-test using the bitbake recipe: spidev-test.bb I set: ARCH=arm BBPATH CROSS_COMPILER=arm-linux-gnueabihf- PATH ... and then tried to build spidev-test: $ bitbake -b spidev-test.bb WARNING: Buildfile specified, dependencies will not be handled. If this is not what you want, do not use -b / --buildfile. Loading cache: 100% |################################################################| Time: 0:00:00 Loaded 1433 entries from dependency cache. Build Configuration: BB_VERSION = "1.49.2" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "fedora-33" TARGET_SYS = "x86_64-oe-linux" MACHINE = "qemux86-64" DISTRO = "nodistro" DISTRO_VERSION = "nodistro.0" TUNE_FEATURES = "m64 core2" TARGET_FPU = "" meta = "master:fa1e1fbc082e82e41ccfeae58af97fe048c9aac7" Initialising tasks: 100% |###########################################################| Time: 0:00:00 Sstate summary: Wanted 6 Local 0 Network 0 Missed 6 Current 0 (0% match, 0% complete) NOTE: Executing Tasks WARNING: spidev-test-1.0-r0 do_populate_lic: Could not copy license file /home/fedora/openembedded-core/meta/files/common-licenses/GPL-2.0 to /home/fedora/openembedded-core/build/tmp-glibc/work/qemux86_64-oe-linux/spidev-test/1.0-r0/license-destdir/spidev-test/GPL-2.0: [Errno 2] No such file or directory: '/home/fedora/openembedded-core/meta/files/common-licenses/GPL-2.0' ERROR: spidev-test-1.0-r0 do_populate_lic: QA Issue: spidev-test: LIC_FILES_CHKSUM points to an invalid file: /home/fedora/openembedded-core/meta/files/common-licenses/GPL-2.0 [license-checksum] ERROR: spidev-test-1.0-r0 do_populate_lic: Fatal QA errors found, failing task. ERROR: Logfile of failure stored in: /home/fedora/openembedded-core/build/tmp-glibc/work/qemux86_64-oe-linux/spidev-test/1.0-r0/temp/log.do_populate_lic.281153 ERROR: Task (/home/fedora/junk/meta-openembedded/meta-oe/recipes-kernel/spidev-test/spidev-test.bb:do_populate_lic) failed with exit code '1' NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to be rerun and 1 failed. Summary: 1 task failed: /home/fedora/junk/meta-openembedded/meta-oe/recipes-kernel/spidev-test/spidev-test.bb:do_populate_lic Summary: There were 2 WARNING messages shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code. What's this about licences? ---John On 2021-03-16 11:50, jchludzinski via lists.yoctoproject.org wrote: > I'm 'bitbaking' now. > > On 2021-03-16 10:53, jchludzinski via lists.yoctoproject.org wrote: Well, because time is of the essence, could you give me a little > assist here and explain how I might build spidev-test using > OpenEmbedded? > > THANKS for your help! > ---John > > On 2021-03-16 05:58, Josef Holzmayr wrote: Am Di., 16. März 2021 um 10:49 Uhr schrieb Nicolas Dechesne > <nicolas.dechesne@linaro.org>: > On Tue, Mar 16, 2021 at 8:07 AM jchludzinski via > lists.yoctoproject.org > <jchludzinski=vivaldi.net@lists.yoctoproject.org> wrote: > It certainly appears to be BUT I'm not certain what I'm looking at? > > What is meta-openembedded? > > Is it a GIT repo that can be cloned and built? > Short answer is yes. The whole Yocto Project / Open Embedded concept > is based around 'layers. A layer is a repository that contains recipes > (and/or machine/distro, ..). The Yocto Project releases include a > couple of common/core layers, but there are plenty of layers out there > which can be used > I am sure there are quite a bit of documentation on this topic, but > perhaps you might want to start with: > https://docs.yoctoproject.org/overview-manual/yp-intro.html#the-yocto-project-layer-model Or grab a beer and start bingewatching https://www.youtube.com/playlist?list=PLD4M5FoHz-TxMfBFrDKfIS_GLY25Qsfyj </SCNR> > How do I use this to build spidev-test? > > ---John > > On 2021-03-15 19:54, akuster wrote: > > On 3/15/21 4:11 PM, jchludzinski via lists.yoctoproject.org wrote: > > I got a piece of code from github: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/spi/spidev_test.c > > I'd like to add it somewhere under /*tools/testing*/ and build it there. > > Not sure if this is appropriate? If so, how do I go about this? > > If not, what's the best way to build this? > > Is this what you are looking for? > https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-kernel/spidev-test/spidev-test.bb > > -armin [-- Attachment #2: Type: text/html, Size: 8727 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [yocto] Building test code? 2021-03-16 18:39 ` jchludzinski @ 2021-03-16 18:43 ` Robert P. J. Day 2021-03-17 15:41 ` jchludzinski 0 siblings, 1 reply; 10+ messages in thread From: Robert P. J. Day @ 2021-03-16 18:43 UTC (permalink / raw) To: jchludzinski Cc: Josef Holzmayr, Nicolas Dechesne, akuster, Yocto, jchludzinski via lists.yoctoproject.org [-- Attachment #1: Type: text/plain, Size: 2810 bytes --] On Tue, 16 Mar 2021, jchludzinski via lists.yoctoproject.org wrote: > I tried to build spidev-test using the bitbake recipe: > > spidev-test.bb > > I set: > ARCH=arm > BBPATH > CROSS_COMPILER=arm-linux-gnueabihf- > PATH > > ... and then tried to build spidev-test: > > $ bitbake -b spidev-test.bb > WARNING: Buildfile specified, dependencies will not be handled. If this is not what you want, do not use -b / --buildfile. > Loading cache: 100% |################################################################| Time: 0:00:00 > Loaded 1433 entries from dependency cache. > > Build Configuration: > BB_VERSION = "1.49.2" > BUILD_SYS = "x86_64-linux" > NATIVELSBSTRING = "fedora-33" > TARGET_SYS = "x86_64-oe-linux" > MACHINE = "qemux86-64" > DISTRO = "nodistro" > DISTRO_VERSION = "nodistro.0" > TUNE_FEATURES = "m64 core2" > TARGET_FPU = "" > meta = "master:fa1e1fbc082e82e41ccfeae58af97fe048c9aac7" > > Initialising tasks: 100% |###########################################################| Time: 0:00:00 > Sstate summary: Wanted 6 Local 0 Network 0 Missed 6 Current 0 (0% match, 0% complete) > NOTE: Executing Tasks > WARNING: spidev-test-1.0-r0 do_populate_lic: Could not copy license file /home/fedora/openembedded-core/meta/files/common-lic > enses/GPL-2.0 to /home/fedora/openembedded-core/build/tmp-glibc/work/qemux86_64-oe-linux/spidev-test/1.0-r0/license-destdir/s > pidev-test/GPL-2.0: [Errno 2] No such file or directory: '/home/fedora/openembedded-core/meta/files/common-licenses/GPL-2.0' > ERROR: spidev-test-1.0-r0 do_populate_lic: QA Issue: spidev-test: LIC_FILES_CHKSUM points to an invalid file: /home/fedora/op > enembedded-core/meta/files/common-licenses/GPL-2.0 [license-checksum] > ERROR: spidev-test-1.0-r0 do_populate_lic: Fatal QA errors found, failing task. > ERROR: Logfile of failure stored in: /home/fedora/openembedded-core/build/tmp-glibc/work/qemux86_64-oe-linux/spidev-test/1.0- > r0/temp/log.do_populate_lic.281153 > ERROR: Task (/home/fedora/junk/meta-openembedded/meta-oe/recipes-kernel/spidev-test/spidev-test.bb:do_populate_lic) failed wi > th exit code '1' > NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to be rerun and 1 failed. > > Summary: 1 task failed: > /home/fedora/junk/meta-openembedded/meta-oe/recipes-kernel/spidev-test/spidev-test.bb:do_populate_lic > Summary: There were 2 WARNING messages shown. > Summary: There were 2 ERROR messages shown, returning a non-zero exit code. > What's this about licences? in current OE, there is no "GPL-2.0" license file, there is "GPL-2.0-only" and "GPL-2.0-or-later" and a bunch of others, so i think you need to pick one of those. rday ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [yocto] Building test code? 2021-03-16 18:43 ` Robert P. J. Day @ 2021-03-17 15:41 ` jchludzinski 0 siblings, 0 replies; 10+ messages in thread From: jchludzinski @ 2021-03-17 15:41 UTC (permalink / raw) To: Robert P. J. Day Cc: Josef Holzmayr, Nicolas Dechesne, akuster, Yocto, jchludzinski via lists.yoctoproject.org [-- Attachment #1: Type: text/plain, Size: 3368 bytes --] There are 2 git repos: _openembedded-core_ and _meta-openembedded._ _openembedded-core_ has _oe-init-build-env_ to create the build environment. _meta-openembedded_ has the recipe for _spidev-test_ If I use _oe-init-build-env_ from _openembedded-core_ to create the env vars then try: $ bitbake -b spidev-test.bb I get into those licencing issues. How do I extricate myself from this conundrum? ---John On 2021-03-16 14:43, Robert P. J. Day wrote: > On Tue, 16 Mar 2021, jchludzinski via lists.yoctoproject.org wrote: > >> I tried to build spidev-test using the bitbake recipe: >> >> spidev-test.bb >> >> I set: >> ARCH=arm >> BBPATH >> CROSS_COMPILER=arm-linux-gnueabihf- >> PATH >> >> ... and then tried to build spidev-test: >> >> $ bitbake -b spidev-test.bb >> WARNING: Buildfile specified, dependencies will not be handled. If this is not what you want, do not use -b / --buildfile. >> Loading cache: 100% |################################################################| Time: 0:00:00 >> Loaded 1433 entries from dependency cache. >> >> Build Configuration: >> BB_VERSION = "1.49.2" >> BUILD_SYS = "x86_64-linux" >> NATIVELSBSTRING = "fedora-33" >> TARGET_SYS = "x86_64-oe-linux" >> MACHINE = "qemux86-64" >> DISTRO = "nodistro" >> DISTRO_VERSION = "nodistro.0" >> TUNE_FEATURES = "m64 core2" >> TARGET_FPU = "" >> meta = "master:fa1e1fbc082e82e41ccfeae58af97fe048c9aac7" >> >> Initialising tasks: 100% |###########################################################| Time: 0:00:00 >> Sstate summary: Wanted 6 Local 0 Network 0 Missed 6 Current 0 (0% match, 0% complete) >> NOTE: Executing Tasks >> WARNING: spidev-test-1.0-r0 do_populate_lic: Could not copy license file /home/fedora/openembedded-core/meta/files/common-lic >> enses/GPL-2.0 to /home/fedora/openembedded-core/build/tmp-glibc/work/qemux86_64-oe-linux/spidev-test/1.0-r0/license-destdir/s >> pidev-test/GPL-2.0: [Errno 2] No such file or directory: '/home/fedora/openembedded-core/meta/files/common-licenses/GPL-2.0' >> ERROR: spidev-test-1.0-r0 do_populate_lic: QA Issue: spidev-test: LIC_FILES_CHKSUM points to an invalid file: /home/fedora/op >> enembedded-core/meta/files/common-licenses/GPL-2.0 [license-checksum] >> ERROR: spidev-test-1.0-r0 do_populate_lic: Fatal QA errors found, failing task. >> ERROR: Logfile of failure stored in: /home/fedora/openembedded-core/build/tmp-glibc/work/qemux86_64-oe-linux/spidev-test/1.0- >> r0/temp/log.do_populate_lic.281153 >> ERROR: Task (/home/fedora/junk/meta-openembedded/meta-oe/recipes-kernel/spidev-test/spidev-test.bb:do_populate_lic) failed wi >> th exit code '1' >> NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to be rerun and 1 failed. >> >> Summary: 1 task failed: >> /home/fedora/junk/meta-openembedded/meta-oe/recipes-kernel/spidev-test/spidev-test.bb:do_populate_lic >> Summary: There were 2 WARNING messages shown. >> Summary: There were 2 ERROR messages shown, returning a non-zero exit code. >> What's this about licences? > > in current OE, there is no "GPL-2.0" license file, there is > "GPL-2.0-only" and "GPL-2.0-or-later" and a bunch of others, so i > think you need to pick one of those. > > rday > > [-- Attachment #2: Type: text/html, Size: 6105 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2021-03-17 15:41 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-15 23:11 Building test code? jchludzinski
2021-03-15 23:54 ` [yocto] " akuster
2021-03-16 7:07 ` jchludzinski
2021-03-16 9:49 ` Nicolas Dechesne
2021-03-16 9:58 ` Josef Holzmayr
2021-03-16 14:53 ` jchludzinski
[not found] ` <166CDA589776C94C.8652@lists.yoctoproject.org>
2021-03-16 15:50 ` jchludzinski
[not found] ` <166CDD724205027D.27789@lists.yoctoproject.org>
2021-03-16 18:39 ` jchludzinski
2021-03-16 18:43 ` Robert P. J. Day
2021-03-17 15:41 ` jchludzinski
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.