Re: [OE-core] Including kernel-devsrc to the SDK while using INCOMPATIBLE_LICENSE
So for anyone that stumbles across this issue it looks like I was
using the kernel-devsrc in the wrong way.
It seems like it is more for kernel module development done on the
target. I was more interesting in having access to
some kernel driver headers so instead I ended up following
https://docs.yoctoproject.org/singleindex.html#using-headers-to-interface-with-devices
Thanks
Den tis 29 mars 2022 kl 08:52 skrev Måns :
>
> Hi,
>
> I am trying to add the kernel-devsrc to the SDK by using
>
> TOOLCHAIN_TARGET_TASK_append = "kernel-devsrc"
>
> My problem is that we are trying to prevent GPLv3 packages by setting
>
> INCOMPATIBLE_LICENSE = "GPL-3.0"
>
> This resulting in an issue because the kernel-devsrc depend on GPLv3 packages
>
> RDEPENDS_${PN} = "bc python flex bison ${TCLIBC}-utils"
>
> We are currently using Thud. We are not shipping the SDK so the
> INCOMPATIBLE_LICENSE is only needed for the image build. Any
> suggestions on the best approach on how to solve this would be really
> appreciated.
>
> Thanks
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#164056):
https://lists.openembedded.org/g/openembedded-core/message/164056
Mute This Topic: https://lists.openembedded.org/mt/90103149/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] Including kernel-devsrc to the SDK while using INCOMPATIBLE_LICENSE
Hi,
I am trying to add the kernel-devsrc to the SDK by using
TOOLCHAIN_TARGET_TASK_append = "kernel-devsrc"
My problem is that we are trying to prevent GPLv3 packages by setting
INCOMPATIBLE_LICENSE = "GPL-3.0"
This resulting in an issue because the kernel-devsrc depend on GPLv3 packages
RDEPENDS_${PN} = "bc python flex bison ${TCLIBC}-utils"
We are currently using Thud. We are not shipping the SDK so the
INCOMPATIBLE_LICENSE is only needed for the image build. Any
suggestions on the best approach on how to solve this would be really
appreciated.
Thanks
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#163738):
https://lists.openembedded.org/g/openembedded-core/message/163738
Mute This Topic: https://lists.openembedded.org/mt/90103149/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] Missing python.h when building ntpsec
For anyone stumbling on this issue the solution is to adjust the
recipe to contain
CFLAGS_append = " -I${STAGING_INCDIR}/${PYTHON_DIR}${PYTHON_ABI}/"
instead of
CFLAGS_append = " -I${PYTHON_INCLUDE_DIR}"
Den tors 10 feb. 2022 kl 12:40 skrev Mans Zigher via
lists.openembedded.org :
>
> Hi,
>
> So Python.h does actually exist. It was just me that was looking for
> the wrong file python.h but the issue is that ntpsec is not able to
> find the h-file
>
> ['arm-oe-linux-gnueabi-gcc', '-march=armv7-a', '-mfpu=neon',
> '-mfloat-abi=hard', '-fstack-protector-strong', '-pie', '-fPIE',
> '-D_FORTIFY_SOURCE=2', '-Wa,--noexecstack', '-Wformat',
> '-Wformat-security', '-Werror=format-security',
> '--sysroot=/home/extmzigher/Workspace/2016platform/python_product/builds/python/tmp-glibc/work/armv7ahf-neon-oe-linux-gnueabi/ntpsec/1.2.1-r0/recipe-sysroot',
> '-DUNITY_EXCLUDE_FLOAT_PRINT', '-fstack-protector-all', '-Wshadow',
> '-Wpacked', '-Wcast-qual', '-Wmissing-declarations',
> '-Wdisabled-optimization', '-Wimplicit-function-declaration',
> '-Winvalid-pch', '-Wpointer-arith', '-Wwrite-strings', '-Winit-self',
> '-Wfloat-equal', '-Wformat', '-Wformat-signedness',
> '-Wformat-security', '-Wsuggest-attribute=noreturn', '-fPIC', '-O1',
> '-Wall', '-Wextra', '-Wmissing-prototypes', '-Wstrict-prototypes',
> '-Wundef', '-Wunused', '-g', '-O2', '-Wa,--noexecstack',
> '-fexpensive-optimizations', '-frename-registers', '-ftree-vectorize',
> '-finline-functions', '-finline-limit=64',
> '-Wno-error=maybe-uninitialized', '-Wno-error=unused-result',
> '-fno-omit-frame-pointer', '-DTARGET_ION_ABI_VERSION=2',
> '-I${PYTHON_INCLUDE_DIR}', '-fPIC', '../../test.c', '-c',
> '-o/home/extmzigher/Workspace/2016platform/python_product/builds/python/tmp-glibc/work/armv7ahf-neon-oe-linux-gnueabi/ntpsec/1.2.1-r0/ntpsec-1.2.1/build/.conf_check_d3b505aa7ab58576b6d76a2fc3091b1f/testbuild/main/test.c.1.o']
> err: ../../test.c:2:10: fatal error: Python.h: No such file or directory
> #include
> ^~
> compilation terminated.
>
> from
> /home/extmzigher/Workspace/2016platform/python_product/builds/python/tmp-glibc/work/armv7ahf-neon-oe-linux-gnueabi/ntpsec/1.2.1-r0/ntpsec-1.2.1/pylib:
> Test does not build: Traceback (most recent call last):
> File
> "/home/extmzigher/Workspace/2016platform/python_product/builds/python/tmp-glibc/work/armv7ahf-neon-oe-linux-gnueabi/ntpsec/1.2.1-r0/ntpsec-1.2.1/.waf-2.0.20-36f5354d605298f6a89c09e0c7ef6c1d/waflib/Configure.py",
> line 335, in run_build
> bld.compile()
> File
> "/home/extmzigher/Workspace/2016platform/python_product/builds/python/tmp-glibc/work/armv7ahf-neon-oe-linux-gnueabi/ntpsec/1.2.1-r0/ntpsec-1.2.1/.waf-2.0.20-36f5354d605298f6a89c09e0c7ef6c1d/waflib/Build.py",
> line 176, in compile
> raise Errors.BuildError(self.producer.error)
> BuildError: Build failed
> -> task in 'testprog' failed with exit status 1 (run with -v to
> display more information)
>
> Could not build python extensions
> from
> /home/extmzigher/Workspace/2016platform/python_product/builds/python/tmp-glibc/work/armv7ahf-neon-oe-linux-gnueabi/ntpsec/1.2.1-r0/ntpsec-1.2.1/pylib
>
> So something is not correct with the include path. But thanks for your help
>
> Thanks,
>
>
> Den ons 9 feb. 2022 kl 18:51 skrev Khem Raj :
> >
> > On Wed, Feb 9, 2022 at 5:50 AM Mans Zigher wrote:
> > >
> > > Hi,
> > >
> > > I am trying to backport ntpsec from master to Thud but I have
> > > encountered an issue where python.h is missing in the sysroot for the
> > > ntpsec so the configuration task is failing. The ntpsec recipe has
> > >
> > > DEPENDS += "bison-native \
> > > openssl \
> > > python3"
> > >
> > > So should that not result in python.h being included to the sysroot
> > > for the ntpsec? Any hints on what to look for?
> > >
> >
> > what happens if you change python3 to python in depends
> >
> > > Thanks,
> > >
> > >
> > >
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161612):
https://lists.openembedded.org/g/openembedded-core/message/161612
Mute This Topic: https://lists.openembedded.org/mt/89021393/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] Missing python.h when building ntpsec
Hi,
So Python.h does actually exist. It was just me that was looking for
the wrong file python.h but the issue is that ntpsec is not able to
find the h-file
['arm-oe-linux-gnueabi-gcc', '-march=armv7-a', '-mfpu=neon',
'-mfloat-abi=hard', '-fstack-protector-strong', '-pie', '-fPIE',
'-D_FORTIFY_SOURCE=2', '-Wa,--noexecstack', '-Wformat',
'-Wformat-security', '-Werror=format-security',
'--sysroot=/home/extmzigher/Workspace/2016platform/python_product/builds/python/tmp-glibc/work/armv7ahf-neon-oe-linux-gnueabi/ntpsec/1.2.1-r0/recipe-sysroot',
'-DUNITY_EXCLUDE_FLOAT_PRINT', '-fstack-protector-all', '-Wshadow',
'-Wpacked', '-Wcast-qual', '-Wmissing-declarations',
'-Wdisabled-optimization', '-Wimplicit-function-declaration',
'-Winvalid-pch', '-Wpointer-arith', '-Wwrite-strings', '-Winit-self',
'-Wfloat-equal', '-Wformat', '-Wformat-signedness',
'-Wformat-security', '-Wsuggest-attribute=noreturn', '-fPIC', '-O1',
'-Wall', '-Wextra', '-Wmissing-prototypes', '-Wstrict-prototypes',
'-Wundef', '-Wunused', '-g', '-O2', '-Wa,--noexecstack',
'-fexpensive-optimizations', '-frename-registers', '-ftree-vectorize',
'-finline-functions', '-finline-limit=64',
'-Wno-error=maybe-uninitialized', '-Wno-error=unused-result',
'-fno-omit-frame-pointer', '-DTARGET_ION_ABI_VERSION=2',
'-I${PYTHON_INCLUDE_DIR}', '-fPIC', '../../test.c', '-c',
'-o/home/extmzigher/Workspace/2016platform/python_product/builds/python/tmp-glibc/work/armv7ahf-neon-oe-linux-gnueabi/ntpsec/1.2.1-r0/ntpsec-1.2.1/build/.conf_check_d3b505aa7ab58576b6d76a2fc3091b1f/testbuild/main/test.c.1.o']
err: ../../test.c:2:10: fatal error: Python.h: No such file or directory
#include
^~
compilation terminated.
from
/home/extmzigher/Workspace/2016platform/python_product/builds/python/tmp-glibc/work/armv7ahf-neon-oe-linux-gnueabi/ntpsec/1.2.1-r0/ntpsec-1.2.1/pylib:
Test does not build: Traceback (most recent call last):
File
"/home/extmzigher/Workspace/2016platform/python_product/builds/python/tmp-glibc/work/armv7ahf-neon-oe-linux-gnueabi/ntpsec/1.2.1-r0/ntpsec-1.2.1/.waf-2.0.20-36f5354d605298f6a89c09e0c7ef6c1d/waflib/Configure.py",
line 335, in run_build
bld.compile()
File
"/home/extmzigher/Workspace/2016platform/python_product/builds/python/tmp-glibc/work/armv7ahf-neon-oe-linux-gnueabi/ntpsec/1.2.1-r0/ntpsec-1.2.1/.waf-2.0.20-36f5354d605298f6a89c09e0c7ef6c1d/waflib/Build.py",
line 176, in compile
raise Errors.BuildError(self.producer.error)
BuildError: Build failed
-> task in 'testprog' failed with exit status 1 (run with -v to
display more information)
Could not build python extensions
from
/home/extmzigher/Workspace/2016platform/python_product/builds/python/tmp-glibc/work/armv7ahf-neon-oe-linux-gnueabi/ntpsec/1.2.1-r0/ntpsec-1.2.1/pylib
So something is not correct with the include path. But thanks for your help
Thanks,
Den ons 9 feb. 2022 kl 18:51 skrev Khem Raj :
>
> On Wed, Feb 9, 2022 at 5:50 AM Mans Zigher wrote:
> >
> > Hi,
> >
> > I am trying to backport ntpsec from master to Thud but I have
> > encountered an issue where python.h is missing in the sysroot for the
> > ntpsec so the configuration task is failing. The ntpsec recipe has
> >
> > DEPENDS += "bison-native \
> > openssl \
> > python3"
> >
> > So should that not result in python.h being included to the sysroot
> > for the ntpsec? Any hints on what to look for?
> >
>
> what happens if you change python3 to python in depends
>
> > Thanks,
> >
> >
> >
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161608):
https://lists.openembedded.org/g/openembedded-core/message/161608
Mute This Topic: https://lists.openembedded.org/mt/89021393/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] Missing python.h when building ntpsec
Hi, I am trying to backport ntpsec from master to Thud but I have encountered an issue where python.h is missing in the sysroot for the ntpsec so the configuration task is failing. The ntpsec recipe has DEPENDS += "bison-native \ openssl \ python3" So should that not result in python.h being included to the sysroot for the ntpsec? Any hints on what to look for? Thanks, -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#161562): https://lists.openembedded.org/g/openembedded-core/message/161562 Mute This Topic: https://lists.openembedded.org/mt/89021393/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [Question] "global" package list used to bump up customer packages
Hi,
Thanks for the reply. My customer are not really interested in going
into multiple recipes so that is why I am thinking of having a
manifest file for them to update packages in one location. I still
want to have some kind of step where someone approves the "pumping" so
even if AUTOREV could be an alternative I am not sure that is the
solution but I will investigate that. The pn-somepackage variable is
likely part of the solution.
BR
Den fre 19 feb. 2021 kl 18:38 skrev Richard Purdie
:
>
> On Fri, 2021-02-19 at 09:53 +0100, Mans Zigher wrote:
> > Hi,
> >
> > I have a problem getting my customer to understand how to work with
> > OE. They have a set of private packages that they continuously need to
> > bump up to use the latest version. The packages are stored up in an
> > artifactory server. I have an idea of maybe helping them out by adding
> > a manifest file containing a couple of entries for each package
> >
> > VERSION = "0.25.6"
> > SRC_URI[md5sum] = "0d6bc46bb69b2a0dce0c042d27b4f25c"
> > SRC_URI[sha256sum] =
> > "c20ea63a5e2f24e25d91e5cdfaa6b4b3735739d6170bea7b2b7d429fc397b718"
> >
> > This manifest should then be pulled into the bitbake environment so
> > that the packages can read these entries and download what is needed.
> > Any comments regarding this potential solution would be greatly
> > appreciated.
> >
> > Also I have a faint memory of seeing something similar solution so if
> > you know if something already exists then I would appreciate if you
> > could let me know.
>
> Are you thinking of AUTOREV? That works if the fetcher has support
> for the source control system being used, e.g. git or subversion but
> I'm not sure it would work for artifactory without a dedicated fetcher
> module.
>
> Certainly generating an include file like this is one way to handle
> this. You can use package-name overrides, e.g.:
>
> VERSION_pn-somepackagename = "0.1.2"
>
> although its harder to do with flags, you might have to put those via
> an intermediate variable:
>
> SRCURISHA256_pn-somepackagename = "XXX"
>
> then in the recipe:
>
> SRC_URI[sha256sum] = "${SRCURISHA256}"
>
> Cheers,
>
> Richard
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#148432):
https://lists.openembedded.org/g/openembedded-core/message/148432
Mute This Topic: https://lists.openembedded.org/mt/80751286/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [Question] "global" package list used to bump up customer packages
Hi, I have a problem getting my customer to understand how to work with OE. They have a set of private packages that they continuously need to bump up to use the latest version. The packages are stored up in an artifactory server. I have an idea of maybe helping them out by adding a manifest file containing a couple of entries for each package VERSION = "0.25.6" SRC_URI[md5sum] = "0d6bc46bb69b2a0dce0c042d27b4f25c" SRC_URI[sha256sum] = "c20ea63a5e2f24e25d91e5cdfaa6b4b3735739d6170bea7b2b7d429fc397b718" This manifest should then be pulled into the bitbake environment so that the packages can read these entries and download what is needed. Any comments regarding this potential solution would be greatly appreciated. Also I have a faint memory of seeing something similar solution so if you know if something already exists then I would appreciate if you could let me know. BR -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#148341): https://lists.openembedded.org/g/openembedded-core/message/148341 Mute This Topic: https://lists.openembedded.org/mt/80751286/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
