date:20230620

[yocto] [meta-security][PATCH] openscap: fix buildpaths issue

2023-06-20 Thread Kai Kang

From: Kai Kang 

Variables PREFERRED_PYTHON_PATH and PYTHON3_PATH are set with
${PYTHON_EXECUTABLE}. For cross compile, ${PYTHON_EXECUTABLE} may point
to other path rather than standard dir such as /usr/bin. Then the
generated library file contains such path which should NOT. Update to
make variables PREFERRED_PYTHON_PATH and PYTHON3_PATH configurable to
fix buildpaths issue:

| WARNING: openscap-1.3.7-r0 do_package_qa: QA Issue: File
| /usr/lib/libopenscap.so.25.5.1 in package openscap contains reference
| to TMPDIR [buildpaths]

Signed-off-by: Kai Kang 
---
 ...ts.txt-make-2-variables-configurable.patch | 37 +++
 .../openscap/openscap_1.3.7.bb|  8 +++-
 2 files changed, 44 insertions(+), 1 deletion(-)
 create mode 100644 
meta-security-compliance/recipes-openscap/openscap/files/0001-CMakeLists.txt-make-2-variables-configurable.patch

diff --git 
a/meta-security-compliance/recipes-openscap/openscap/files/0001-CMakeLists.txt-make-2-variables-configurable.patch
 
b/meta-security-compliance/recipes-openscap/openscap/files/0001-CMakeLists.txt-make-2-variables-configurable.patch
new file mode 100644
index 000..953b0d9
--- /dev/null
+++ 
b/meta-security-compliance/recipes-openscap/openscap/files/0001-CMakeLists.txt-make-2-variables-configurable.patch
@@ -0,0 +1,37 @@
+From f99c3f1f516a84d33794f8e3da59adea1a12ef54 Mon Sep 17 00:00:00 2001
+From: Kai Kang 
+Date: Tue, 20 Jun 2023 22:42:51 +0800
+Subject: [PATCH] CMakeLists.txt: make 2 variables configurable
+
+Variables PREFERRED_PYTHON_PATH and PYTHON3_PATH are set with
+${PYTHON_EXECUTABLE}. For cross compile, ${PYTHON_EXECUTABLE} may point
+to other path rather than standard dir such as /usr/bin. Then the
+generated library file contains such path which should NOT. Update to
+make variables PREFERRED_PYTHON_PATH and PYTHON3_PATH configurable to
+avoid such issue.
+
+Upstream-Status: Submitted [https://github.com/OpenSCAP/openscap/pull/1990]
+
+Signed-off-by: Kai Kang 
+---
+ CMakeLists.txt | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index 5db014e77..74628cdd4 100644
+--- a/CMakeLists.txt
 b/CMakeLists.txt
+@@ -125,8 +125,8 @@ endif()
+ find_package(PythonInterp 3)
+ find_package(PythonLibs 3)
+ 
+-set(PREFERRED_PYTHON_PATH "${PYTHON_EXECUTABLE}")
+-set(PYTHON3_PATH "${PYTHON_EXECUTABLE}")
++set(PREFERRED_PYTHON_PATH "${PYTHON_EXECUTABLE}" CACHE PATH "Path to 
preferred Python")
++set(PYTHON3_PATH "${PYTHON_EXECUTABLE}" CACHE PATH "Path to Python3")
+ 
+ find_package(RPM)
+ if(RPM_FOUND)
+-- 
+2.34.1
+
diff --git 
a/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.7.bb 
b/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.7.bb
index cfe93f0..5ad92d4 100644
--- a/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.7.bb
+++ b/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.7.bb
@@ -7,7 +7,13 @@ require openscap.inc
 inherit systemd
 
 SRCREV = "55efbfda0f617e05862ab6ed4862e10dbee52b03"
-SRC_URI = 
"git://github.com/OpenSCAP/openscap.git;branch=maint-1.3;protocol=https"
+SRC_URI = 
"git://github.com/OpenSCAP/openscap.git;branch=maint-1.3;protocol=https \
+   file://0001-CMakeLists.txt-make-2-variables-configurable.patch \
+   "
+
+EXTRA_OECMAKE += "-DPREFERRED_PYTHON_PATH=${bindir}/python3 \
+  -DPYTHON3_PATH=${bindir}/python3 \
+  "
 
 SYSTEMD_PACKAGES = "${PN}"
 SYSTEMD_SERVICE:${PN} = "oscap-remediate.service"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60368): https://lists.yoctoproject.org/g/yocto/message/60368
Mute This Topic: https://lists.yoctoproject.org/mt/99670413/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-security][PATCH] openscap: Update to tip to get OE/Poky support

2023-06-20 Thread Armin Kuster

Drop changes now in upstream.

Signed-off-by: Armin Kuster 
---
 .../0001-openscap-Add-openembedded.patch  | 128 --
 .../0002-openembedded-add-Poky-distro.patch   |  80 ---
 recipes-compliance/openscap/openscap_1.3.7.bb |   6 +-
 3 files changed, 2 insertions(+), 212 deletions(-)
 delete mode 100644 
recipes-compliance/openscap/files/0001-openscap-Add-openembedded.patch
 delete mode 100644 
recipes-compliance/openscap/files/0002-openembedded-add-Poky-distro.patch

diff --git 
a/recipes-compliance/openscap/files/0001-openscap-Add-openembedded.patch 
b/recipes-compliance/openscap/files/0001-openscap-Add-openembedded.patch
deleted file mode 100644
index 1af72bb..000
--- a/recipes-compliance/openscap/files/0001-openscap-Add-openembedded.patch
+++ /dev/null
@@ -1,128 +0,0 @@
-From 8f8b580a882e9584e2b3726dab2c3f8e01cb885f Mon Sep 17 00:00:00 2001
-From: Armin Kuster 
-Date: Sun, 4 Jun 2023 20:16:12 -0400
-Subject: [PATCH 1/2] openscap: Add openembedded
-
-Signed-off-by: Armin Kuster 
-
-Upstream-Status: Pending
-Signed-off-by: Armin Kuster 
-

- cpe/openscap-cpe-dict.xml |  5 +++
- cpe/openscap-cpe-oval.xml | 45 +--
- src/OVAL/probes/unix/runlevel_probe.c |  8 -
- 3 files changed, 47 insertions(+), 11 deletions(-)
-
-diff --git a/cpe/openscap-cpe-dict.xml b/cpe/openscap-cpe-dict.xml
-index 02d536189..3338a9e55 100644
 a/cpe/openscap-cpe-dict.xml
-+++ b/cpe/openscap-cpe-dict.xml
-@@ -53,4 +53,9 @@
- Fedora 35
- http://oval.mitre.org/XMLSchema/oval-definitions-5"; 
href="openscap-cpe-oval.xml">oval:org.open-scap.cpe.fedora:def:35
-   
-+  
-+OpenEmbedded all versions
-+http://oval.mitre.org/XMLSchema/oval-definitions-5"; 
href="openscap-cpe-oval.xml">oval:org.open-scap.cpe.openembedded:def:1
-+  
-+
- 
-diff --git a/cpe/openscap-cpe-oval.xml b/cpe/openscap-cpe-oval.xml
-index 64099400b..2f3e25419 100644
 a/cpe/openscap-cpe-oval.xml
-+++ b/cpe/openscap-cpe-oval.xml
-@@ -821,6 +821,20 @@
- 
-   
- 
-+
-+  
-+OpenEmbedded Org
-+
-+OpenEmbedded Nodistro
-+
-+
-+OpenEmbedded No Distro is 
installed
-+  
-+  
-+
-+
-+  
-+
-   
-   
- SOFTWARE\Microsoft\Windows NT\CurrentVersion
-   ProductName
- 
--http://oval.mitre.org/XMLSchema/oval-definitions-5#independent";>
--  /etc/os-release
--  ^ID="(\w+)"$
--  1
--
--http://oval.mitre.org/XMLSchema/oval-definitions-5#independent";>
--  /etc/os-release
--  ^VERSION_ID="(\d)"$
--  1
--
-+http://oval.mitre.org/XMLSchema/oval-definitions-5#unix"; version="1" 
id="oval:org.open-scap.cpe.openembedded-release:obj:1" >
-+/etc/os-release
-+
-+http://oval.mitre.org/XMLSchema/oval-definitions-5#independent";
-+>
-+/etc
-+os-release
-+^VERSION=.(\d*.\d*)
-+1
-   
-   
- http://oval.mitre.org/XMLSchema/oval-definitions-5#independent";>
-@@ -1455,5 +1472,13 @@
- http://oval.mitre.org/XMLSchema/oval-definitions-5#windows";>
-   ^.*2016.*$
- 
-+http://oval.mitre.org/XMLSchema/oval-definitions-5#independent";
-+>
-+  4.2
-+
-   
- 
-diff --git a/src/OVAL/probes/unix/runlevel_probe.c 
b/src/OVAL/probes/unix/runlevel_probe.c
-index 7a94b23fc..00a5b85f6 100644
 a/src/OVAL/probes/unix/runlevel_probe.c
-+++ b/src/OVAL/probes/unix/runlevel_probe.c
-@@ -403,6 +403,11 @@ static int is_wrlinux(void)
-   return parse_os_release("cpe:/o:windriver:wrlinux");
- }
- 
-+static int is_openembedded(void)
-+{
-+  return parse_os_release("cpe:/o:openembedded:nodistro");
-+}
-+
- static int is_common (void)
- {
- return (1);
-@@ -424,7 +429,8 @@ const distro_tbl_t distro_tbl[] = {
- { &is_suse, &get_runlevel_suse },
- { &is_solaris,  &get_runlevel_redhat   },
- { &is_wrlinux,  &get_runlevel_wrlinux  },
--{ &is_common,   &get_runlevel_common   }
-+{ &is_common,   &get_runlevel_common   },
-+{ &is_openembedded,  &get_runlevel_common  }
- };
- 
- #define DISTRO_TBL_SIZE ((sizeof distro_tbl)/sizeof (distro_tbl_t))
--- 
-2.25.1
-
diff --git 
a/recipes-compliance/openscap/files/0002-openembedded-add-Poky-distro.patch 
b/recipes-compliance/openscap/files/0002-openembedded-add-Poky-distro.patch
deleted f

[yocto] Yocto Project Status 20 June 2023 (WW25)

2023-06-20 Thread Stephen Jolley

Current Dev Position: YP 4.3 M2

Next Deadline: 17th July 2023 YP 4.3 M2 build date

 

Next Team Meetings:

*   Bug Triage meeting Thursday June 22nd 7:30 am PDT (

https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*   Weekly Project Engineering Sync Tuesday June 20th at 8 am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Twitch -  See  
https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*   YP 4.3 M1 was released
*   YP 3.1.26 is in QA
*   The project has some exciting plans in progress and we're now in the
fortunate position of seeking quotations for some development work. For more
details please see this page on our website:

 

https://www.yoctoproject.org/community/yocto-project-engineering-request-for
-quotation/

*   The automated regression reporting saw some issues for the M1 report
so this is being worked on.
*   There are pending patches to enable layer- overrides
which is particularly useful for enabling layer specific QA checks. This
does bring some changes of behavior for QA checks on bbappends
*   usrmerge is now enabled by default for poky-altcfg, in preparation
for the changes being required by systemd.
*   The 6.1 kernel hang regression was identified and we reverted the
problematic patch until the correct fix merges and filters through the
stable kernel trees.
*   There have been a lot of ptest issues this week, not least after
issues with "No-section" tracebacks were fixed, leading to an increase in
reported failures as that was masking issues. There are some fixes proposed
for ptest-runner but further help is needed on the various failures.
*   We have been approached by a potential new maintainer for the
eclipse plugins. There were some questions about who was still using it and
what the test matrix should look like so please let us know if you are and
we can connect you.
*   The tunctl functionality for runqemu has been dropped as the ip tool
can handle everything needed.

 

Ways to contribute:

*   As people are likely aware, the project has a number of components
which are either unmaintained, or have people with little to no time trying
to keep them alive. These components include: patchtest, layerindex,
devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more.
Many have open bugs. Help is welcome in trying to better look after these
components!
*   There are bugs identified as possible for newcomers to the project:

https://wiki.yoctoproject.org/wiki/Newcomers
*   There are bugs that are currently unassigned for YP 4.3. See:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.3_Unassigned_Enhan
cements.2FBugs
*   We'd welcome new maintainers for recipes in OE-Core. Please see the
list at:

http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.inc and discuss with the existing maintainer, or ask on the OE-Core
mailing list. We will likely move a chunk of these to "Unassigned" soon to
help facilitate this.
*   Help is very much welcome in trying to resolve our autobuilder
intermittent issues. You can see the list of failures we're continuing to
see by searching for the "AB-INT" tag in bugzilla:

https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT.
*   Help us resolve CVE issues:
 CVE metrics 
*   We have a growing number of bugs in bugzilla, any help with them is
appreciated.

 

YP 4.3 Milestone Dates:

*   YP 4.3 M1 is released
*   YP 4.3 M2 build date  2023/07/17
*   YP 4.3 M2 Release date 2023/07/28
*   YP 4.3 M3 build date  2023/08/28
*   YP 4.3 M3 Release date 2023/09/08
*   YP 4.3 M4 build date  2023/10/02
*   YP 4.3 M4 Release date 2023/10/27

 

Upcoming dot releases:

*   YP 3.1.26 is in QA
*   YP 4.0.11 build date 2023/06/26
*   YP 4.0.11 Release date 2023/07/07
*   YP 4.2.2 build date 2023/07/10
*   YP 4.2.2 Release date 2023/07/21 
*   YP 3.1.27 build date 2023/07/31
*   YP 3.1.27 Release date 2023/08/11
*   YP 4.0.12 build date 2023/08/07
*   YP 4.0.12 Release date 2023/08/18
*   YP 4.2.3 build date 2023/08/28
*   YP 4.2.3 Release date 2023/09/08
*   YP 3.1.28 build date 2023/09/18
*   YP 3.1.28 Release date 2023/09/29
*   YP 4.0.13 build date 202

[yocto] Request for Quotations for development work

2023-06-20 Thread Richard Purdie

Hi All,

The project has some exciting plans in progress and I'm happy to say
we're now in the fortunate position that we're able to seek quotations
for some development work. For more details please see this page on
website:

https://www.yoctoproject.org/community/yocto-project-engineering-request-for-quotation/

Please feel free to reach out to me or the Yocto Project TSC if there
are any questions.

Regards,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60365): https://lists.yoctoproject.org/g/yocto/message/60365
Mute This Topic: https://lists.yoctoproject.org/mt/99644713/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: 
https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

2023-06-20 Thread Ross Burton

So there’s a lot of settings in that file.  Can you replicate with a default 
config as generated by poky?

Ross

> On 20 Jun 2023, at 14:44, Jesus Jimenez Sanchez 
>  wrote:
>
> Hello,
>
> I am using an absolute path there; I just removed it before posting on the 
> email thread.
>
> I have attached my local.conf here.
>
> Best regards,
> Jesús Jiménez SánchezFrom: Sumit Garg 
> Sent: Tuesday 20 June 2023 14:18
> To: Ross Burton 
> Cc: Jesus Jimenez Sanchez ; 
> yocto@lists.yoctoproject.org 
> Subject: Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain
>  [You don't often get email from sumit.g...@linaro.org. Learn why this is 
> important at https://aka.ms/LearnAboutSenderIdentification ]
>
> CAUTION: This email originated from outside of our organization. Do not click 
> links or open attachments unless you recognize the sender and know the 
> content is safe.
>
>
> On Tue, 20 Jun 2023 at 18:06, Ross Burton  wrote:
> >
> > On 20 Jun 2023, at 13:08, Sumit Garg via lists.yoctoproject.org 
> >  wrote:
> > >
> > > On Mon, 19 Jun 2023 at 22:03, Jesus.JimenezSanchez via
> > > lists.yoctoproject.org
> > >  wrote:
> > >>
> > >> Hello, I'm trying to add the arm toolchain to my yocto project but I 
> > >> just got this error
> > >> ```
> > >> | cp: cannot stat 
> > >> '.../tmp-glibc/work/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/external-arm-toolchain/2022.02-r0/image/local/SUPPORTED':
> > >>  No such file or directory
> > >> ```
> > >> It comes from the `external-arm-toolchain.bb` recipe. I've checked and 
> > >> the `SUPPORTED` file is in the right folder (the `files` folder where 
> > >> the `external-arm-toolchain.bb` file is). I haven't made any 
> > >> modifications to the meta-arm repo. I just cloned it and changed to 
> > >> branch `kirkstone`. After that, I have configured my local.conf with 
> > >> this:
> > >> ```
> > >> TCMODE = "external-arm"
> > >>
> > >> EXTERNAL_TOOLCHAIN = 
> > >> ".../gcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihf"
> > >> ```
> > >>
> > >
> > > Don't provide a relative path here. It should be an absolute path to
> > > your external toolchain install directory. This should resolve your
> > > issue.
> >
> > If that’s the issue, can you add a check for the path being absolute to the 
> > class?
> >
>
> Sure, see [1].
>
> [1] https://lists.yoctoproject.org/g/meta-arm/message/4809
>
> -Sumit
>
> > Ross
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60364): https://lists.yoctoproject.org/g/yocto/message/60364
Mute This Topic: https://lists.yoctoproject.org/mt/99626981/21656
Mute #toolchain:https://lists.yoctoproject.org/g/yocto/mutehashtag/toolchain
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: 
https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

2023-06-20 Thread Jesus Jimenez Sanchez via lists.yoctoproject.org

Hello,

I am using an absolute path there; I just removed it before posting on the 
email thread.

I have attached my local.conf here.

Best regards,
Jesús Jiménez Sánchez

From: Sumit Garg 
Sent: Tuesday 20 June 2023 14:18
To: Ross Burton 
Cc: Jesus Jimenez Sanchez ; 
yocto@lists.yoctoproject.org 
Subject: Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

[You don't often get email from sumit.g...@linaro.org. Learn why this is 
important at https://aka.ms/LearnAboutSenderIdentification ]

CAUTION: This email originated from outside of our organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.


On Tue, 20 Jun 2023 at 18:06, Ross Burton  wrote:
>
> On 20 Jun 2023, at 13:08, Sumit Garg via lists.yoctoproject.org 
>  wrote:
> >
> > On Mon, 19 Jun 2023 at 22:03, Jesus.JimenezSanchez via
> > lists.yoctoproject.org
> >  wrote:
> >>
> >> Hello, I'm trying to add the arm toolchain to my yocto project but I just 
> >> got this error
> >> ```
> >> | cp: cannot stat 
> >> '.../tmp-glibc/work/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/external-arm-toolchain/2022.02-r0/image/local/SUPPORTED':
> >>  No such file or directory
> >> ```
> >> It comes from the `external-arm-toolchain.bb` recipe. I've checked and the 
> >> `SUPPORTED` file is in the right folder (the `files` folder where the 
> >> `external-arm-toolchain.bb` file is). I haven't made any modifications to 
> >> the meta-arm repo. I just cloned it and changed to branch `kirkstone`. 
> >> After that, I have configured my local.conf with this:
> >> ```
> >> TCMODE = "external-arm"
> >>
> >> EXTERNAL_TOOLCHAIN = 
> >> ".../gcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihf"
> >> ```
> >>
> >
> > Don't provide a relative path here. It should be an absolute path to
> > your external toolchain install directory. This should resolve your
> > issue.
>
> If that’s the issue, can you add a check for the path being absolute to the 
> class?
>

Sure, see [1].

[1] 
https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.yoctoproject.org%2Fg%2Fmeta-arm%2Fmessage%2F4809&data=05%7C01%7CJesus.JimenezSanchez%40verifone.com%7C973f208b0af44819944408db7190e99c%7C611a22d68c40495884e3ce47d8205d98%7C0%7C0%7C638228639435319950%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=F7k3iyXYd8FFpc%2FMk2cPW3fKzKxIS44htt85A3liStA%3D&reserved=0

-Sumit

> Ross


local.conf.sample
Description: local.conf.sample

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60363): https://lists.yoctoproject.org/g/yocto/message/60363
Mute This Topic: https://lists.yoctoproject.org/mt/99626981/21656
Mute #toolchain:https://lists.yoctoproject.org/g/yocto/mutehashtag/toolchain
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

2023-06-20 Thread Sumit Garg

On Tue, 20 Jun 2023 at 18:06, Ross Burton  wrote:
>
> On 20 Jun 2023, at 13:08, Sumit Garg via lists.yoctoproject.org 
>  wrote:
> >
> > On Mon, 19 Jun 2023 at 22:03, Jesus.JimenezSanchez via
> > lists.yoctoproject.org
> >  wrote:
> >>
> >> Hello, I'm trying to add the arm toolchain to my yocto project but I just 
> >> got this error
> >> ```
> >> | cp: cannot stat 
> >> '.../tmp-glibc/work/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/external-arm-toolchain/2022.02-r0/image/local/SUPPORTED':
> >>  No such file or directory
> >> ```
> >> It comes from the `external-arm-toolchain.bb` recipe. I've checked and the 
> >> `SUPPORTED` file is in the right folder (the `files` folder where the 
> >> `external-arm-toolchain.bb` file is). I haven't made any modifications to 
> >> the meta-arm repo. I just cloned it and changed to branch `kirkstone`. 
> >> After that, I have configured my local.conf with this:
> >> ```
> >> TCMODE = "external-arm"
> >>
> >> EXTERNAL_TOOLCHAIN = 
> >> ".../gcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihf"
> >> ```
> >>
> >
> > Don't provide a relative path here. It should be an absolute path to
> > your external toolchain install directory. This should resolve your
> > issue.
>
> If that’s the issue, can you add a check for the path being absolute to the 
> class?
>

Sure, see [1].

[1] https://lists.yoctoproject.org/g/meta-arm/message/4809

-Sumit

> Ross

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60362): https://lists.yoctoproject.org/g/yocto/message/60362
Mute This Topic: https://lists.yoctoproject.org/mt/99626981/21656
Mute #toolchain:https://lists.yoctoproject.org/g/yocto/mutehashtag/toolchain
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

2023-06-20 Thread Ross Burton

On 20 Jun 2023, at 13:08, Sumit Garg via lists.yoctoproject.org 
 wrote:
> 
> On Mon, 19 Jun 2023 at 22:03, Jesus.JimenezSanchez via
> lists.yoctoproject.org
>  wrote:
>> 
>> Hello, I'm trying to add the arm toolchain to my yocto project but I just 
>> got this error
>> ```
>> | cp: cannot stat 
>> '.../tmp-glibc/work/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/external-arm-toolchain/2022.02-r0/image/local/SUPPORTED':
>>  No such file or directory
>> ```
>> It comes from the `external-arm-toolchain.bb` recipe. I've checked and the 
>> `SUPPORTED` file is in the right folder (the `files` folder where the 
>> `external-arm-toolchain.bb` file is). I haven't made any modifications to 
>> the meta-arm repo. I just cloned it and changed to branch `kirkstone`. After 
>> that, I have configured my local.conf with this:
>> ```
>> TCMODE = "external-arm"
>> 
>> EXTERNAL_TOOLCHAIN = 
>> ".../gcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihf"
>> ```
>> 
> 
> Don't provide a relative path here. It should be an absolute path to
> your external toolchain install directory. This should resolve your
> issue.

If that’s the issue, can you add a check for the path being absolute to the 
class?

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60361): https://lists.yoctoproject.org/g/yocto/message/60361
Mute This Topic: https://lists.yoctoproject.org/mt/99626981/21656
Mute #toolchain:https://lists.yoctoproject.org/g/yocto/mutehashtag/toolchain
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: 
https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

2023-06-20 Thread Sumit Garg

On Mon, 19 Jun 2023 at 22:03, Jesus.JimenezSanchez via
lists.yoctoproject.org
 wrote:
>
> Hello, I'm trying to add the arm toolchain to my yocto project but I just got 
> this error
> ```
> | cp: cannot stat 
> '.../tmp-glibc/work/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/external-arm-toolchain/2022.02-r0/image/local/SUPPORTED':
>  No such file or directory
> ```
> It comes from the `external-arm-toolchain.bb` recipe. I've checked and the 
> `SUPPORTED` file is in the right folder (the `files` folder where the 
> `external-arm-toolchain.bb` file is). I haven't made any modifications to the 
> meta-arm repo. I just cloned it and changed to branch `kirkstone`. After 
> that, I have configured my local.conf with this:
> ```
> TCMODE = "external-arm"
>
> EXTERNAL_TOOLCHAIN = 
> ".../gcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihf"
> ```
>

Don't provide a relative path here. It should be an absolute path to
your external toolchain install directory. This should resolve your
issue.

-Sumit

> I have added this to the `bblayers.conf`:
> ```
> BBLAYERS += "${OEROOT}/layers/meta-arm/meta-arm-toolchain"
> ```
>
> And that's it, I think. Have I missed any steps?
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60360): https://lists.yoctoproject.org/g/yocto/message/60360
Mute This Topic: https://lists.yoctoproject.org/mt/99626981/21656
Mute #toolchain:https://lists.yoctoproject.org/g/yocto/mutehashtag/toolchain
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

2023-06-20 Thread Ross Burton

On 20 Jun 2023, at 11:35, Jesus Jimenez Sanchez 
 wrote:
> 
> | cp: cannot stat 
> '.../tmp-glibc/work/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/external-arm-toolchain/2022.02-r0/image/local/SUPPORTED':
>  No such file or directory

That’s the line which confuses me.

My line is:

cp -fpPR 
/yocto/ross/build/tmp/work/cortexa15t2hf-neon-poky-linux-gnueabi/external-arm-toolchain/12.2.Rel1-r0/SUPPORTED
 $dest

Do you have local configuration?  I just grabbed poky and meta-arm kirkstone, 
set the two variables, and it built fine.

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60359): https://lists.yoctoproject.org/g/yocto/message/60359
Mute This Topic: https://lists.yoctoproject.org/mt/99626981/21656
Mute #toolchain:https://lists.yoctoproject.org/g/yocto/mutehashtag/toolchain
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: 
https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

2023-06-20 Thread Jesus Jimenez Sanchez via lists.yoctoproject.org

Hello,

This is the complete output from yocto:

```
NOTE: Executing Tasks
ERROR: external-arm-toolchain-2022.02-r0 do_stash_locale: 
ExecutionError('.../tmp-glibc/work/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/external-arm-toolchain/2022.02-r0/temp/run.do_stash_locale.449',
 1, None, None)
ERROR: Logfile of failure stored in: 
.../tmp-glibc/work/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/external-arm-toolchain/2022.02-r0/temp/log.do_stash_locale.449
Log data follows:
| DEBUG: Executing python function sstate_task_prefunc
| DEBUG: Python function sstate_task_prefunc finished
| DEBUG: Executing shell function do_stash_locale
| cp: cannot stat 
'.../tmp-glibc/work/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/external-arm-toolchain/2022.02-r0/image/local/SUPPORTED':
 No such file or directory
| WARNING: 
.../tmp-glibc/work/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/external-arm-toolchain/2022.02-r0/temp/run.do_stash_locale.449:165
 exit 1 from 'cp -fpPR 
.../tmp-glibc/work/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/external-arm-toolchain/2022.02-r0/image/local/SUPPORTED
 $dest'
| WARNING: Backtrace (BB generated script):
| #1: do_stash_locale, 
.../tmp-glibc/work/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/external-arm-toolchain/2022.02-r0/temp/run.do_stash_locale.449,
 line 165
| #2: main, 
.../tmp-glibc/work/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/external-arm-toolchain/2022.02-r0/temp/run.do_stash_locale.449,
 line 177
ERROR: Task 
(.../layers/meta-arm/meta-arm-toolchain/recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb:do_stash_locale)
 failed with exit code '1'
NOTE: Tasks Summary: Attempted 2402 tasks of which 2396 didn't need to be rerun 
and 1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 4 seconds

Summary: 1 task failed:

.../layers/meta-arm/meta-arm-toolchain/recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb:do_stash_locale
Summary: There was 1 ERROR message, returning a non-zero exit code.
```

Best regards,
Jesús Jiménez Sánchez

From: Ross Burton 
Sent: Tuesday 20 June 2023 10:11
To: Jesus Jimenez Sanchez 
Cc: Yocto-mailing-list ; 
meta-...@lists.yoctoproject.org 
Subject: Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

[You don't often get email from ross.bur...@arm.com. Learn why this is 
important at https://aka.ms/LearnAboutSenderIdentification ]

CAUTION: This email originated from outside of our organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Copying meta-arm, as that’s the best place to discuss this.

> On 19 Jun 2023, at 17:33, Jesus.JimenezSanchez via lists.yoctoproject.org 
>  wrote:
>
> Hello, I'm trying to add the arm toolchain to my yocto project but I just got 
> this error
> ```
> | cp: cannot stat 
> '.../tmp-glibc/work/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/external-arm-toolchain/2022.02-r0/image/local/SUPPORTED':
>  No such file or directory
> ```
> It comes from the `external-arm-toolchain.bb` recipe. I've checked and the 
> `SUPPORTED` file is in the right folder (the `files` folder where the 
> `external-arm-toolchain.bb` file is). I haven't made any modifications to the 
> meta-arm repo. I just cloned it and changed to branch `kirkstone`. After 
> that, I have configured my local.conf with this:
> ```
> TCMODE = "external-arm"
>
> EXTERNAL_TOOLCHAIN = 
> ".../gcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihf"
> ```
>
> I have added this to the `bblayers.conf`:
> ```
> BBLAYERS += "${OEROOT}/layers/meta-arm/meta-arm-toolchain"
> ```

Can you share the full logs, instead of just one line?

Also replicating with just poky+meta-arm and a brand new build tree (so no 
local configuration or layers) would help debug.

Ross

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60358): https://lists.yoctoproject.org/g/yocto/message/60358
Mute This Topic: https://lists.yoctoproject.org/mt/99626981/21656
Mute #toolchain:https://lists.yoctoproject.org/g/yocto/mutehashtag/toolchain
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

2023-06-20 Thread Ross Burton

Copying meta-arm, as that’s the best place to discuss this.


> On 19 Jun 2023, at 17:33, Jesus.JimenezSanchez via lists.yoctoproject.org 
>  wrote:
> 
> Hello, I'm trying to add the arm toolchain to my yocto project but I just got 
> this error
> ```
> | cp: cannot stat 
> '.../tmp-glibc/work/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/external-arm-toolchain/2022.02-r0/image/local/SUPPORTED':
>  No such file or directory
> ```
> It comes from the `external-arm-toolchain.bb` recipe. I've checked and the 
> `SUPPORTED` file is in the right folder (the `files` folder where the 
> `external-arm-toolchain.bb` file is). I haven't made any modifications to the 
> meta-arm repo. I just cloned it and changed to branch `kirkstone`. After 
> that, I have configured my local.conf with this:
> ```
> TCMODE = "external-arm"
> 
> EXTERNAL_TOOLCHAIN = 
> ".../gcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihf"
> ```
> 
> I have added this to the `bblayers.conf`:
> ```
> BBLAYERS += "${OEROOT}/layers/meta-arm/meta-arm-toolchain"
> ```

Can you share the full logs, instead of just one line?

Also replicating with just poky+meta-arm and a brand new build tree (so no 
local configuration or layers) would help debug.

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60357): https://lists.yoctoproject.org/g/yocto/message/60357
Mute This Topic: https://lists.yoctoproject.org/mt/99626981/21656
Mute #toolchain:https://lists.yoctoproject.org/g/yocto/mutehashtag/toolchain
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: 
https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Out of tree driver file compilation error

2023-06-20 Thread MOHAMMED HASSAN

Hi guys,
I am trying to load TI bq2429x drivers into my yocto image. I face errors
when at the do_compile stage. At first glance it looks to be a c program
cross compilation error. I think the issue is due to not being able to link
with the header files.
The error I see on my screen.
ERROR: bq2429x-charger-0.1-r0 do_compile: oe_runmake failed
ERROR: bq2429x-charger-0.1-r0 do_compile: Execution of
'/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/temp/run.do_compile.322928'
failed with exit code 1
ERROR: Logfile of failure stored in:
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/temp/log.do_compile.322928
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4
KERNEL_SRC=/home/mohan/amlogic/build/tmp/work-shared/mesons4-lib32-ap222/kernel-source
KERNEL_PATH=/home/mohan/amlogic/build/tmp/work-shared/mesons4-lib32-ap222/kernel-source
KERNEL_VERSION=5.4.180-amlogic CC=aarch64-poky-linux-gcc   -fuse-ld=bfd
-fdebug-prefix-map=/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0=/usr/src/debug/bq2429x-charger/0.1-r0

-fdebug-prefix-map=/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/recipe-sysroot=

-fdebug-prefix-map=/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/recipe-sysroot-native=

 
-fdebug-prefix-map=/home/mohan/amlogic/build/tmp/work-shared/mesons4-lib32-ap222/kernel-source=/usr/src/kernel
LD=aarch64-poky-linux-ld.bfd   AR=aarch64-poky-linux-ar
 
O=/home/mohan/amlogic/build/tmp/work-shared/mesons4-lib32-ap222/kernel-build-artifacts
KBUILD_EXTRA_SYMBOLS=
| make -C
/home/mohan/amlogic/build/tmp/work-shared/mesons4-lib32-ap222/kernel-source
M=/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0
| make[1]: Entering directory '/home/mohan/amlogic/aml-comp/kernel/aml-5.4'
| make[2]: Entering directory
'/home/mohan/amlogic/build/tmp/work-shared/mesons4-lib32-ap222/kernel-build-artifacts'
|   AR
 
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/built-in.a
|   CC [M]
 
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.o
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:37:
error: "BQ2429X_OTG_ENABLE" redefined [-Werror]
|37 | #define BQ2429X_OTG_ENABLE  0x00
|   |
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:36:
note: this is the location of the previous definition
|36 | #define BQ2429X_OTG_ENABLE  0x01
|   |
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:
In function 'bq2429x_disable_otg':
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:317:14:
error: 'BQ2429X_OTG_DISABLE' undeclared (first use in this function); did
you mean 'BQ2429X_WD_DISABLE'?
|   317 | u8 val = BQ2429X_OTG_DISABLE << BQ2429x_OTG_SHIFT;
|   |  ^~~
|   |  BQ2429X_WD_DISABLE
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:317:14:
note: each undeclared identifier is reported only once for each function it
appears in
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:317:37:
error: 'BQ2429x_OTG_SHIFT' undeclared (first use in this function); did you
mean 'BQ2429X_OTG_SHIFT'?
|   317 | u8 val = BQ2429X_OTG_DISABLE << BQ2429x_OTG_SHIFT;
|   | ^
|   | BQ2429X_OTG_SHIFT
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:
At top level:
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:323:63:
error: function declaration isn't a prototype [-Werror=strict-prototypes]
|   323 | static int bq2429x_set_chargecurrent(struct bq2429x *bq, enum
bq2429x_charge_current current)
|   |
^~
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:
In function 'bq2429x_set_chargevoltage':
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:349:6:
error: unused variable 'ret' [-Werror=unused-variable]
|   349 |  int ret;
|   |  ^~~
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:
In function 'bq2429x_set_input_volt_limit':
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:373:6:
error: unused variable 'ret' [-Werror=unuse

[yocto] [meta-security][PATCH] openscap: fix buildpaths issue

[yocto] [meta-security][PATCH] openscap: Update to tip to get OE/Poky support

[yocto] Yocto Project Status 20 June 2023 (WW25)

[yocto] Request for Quotations for development work

Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

Re: [yocto] meta-arm-toolchain: SUPPORTED file not found #toolchain

[yocto] Out of tree driver file compilation error

13 matches

Site Navigation

Mail list logo

Footer information