|
Re: Possible to replace gcc-runtime libraries & libgcc
#gplv3
#yocto
#llvm
The GCC exception frees you from having to fulfil the terms of gpl3 in almost all cases. Links with details are easily obtainable with google search.
Alex
The GCC exception frees you from having to fulfil the terms of gpl3 in almost all cases. Links with details are easily obtainable with google search.
Alex
|
By
Alexander Kanavin
·
#59008
·
|
|
Possible to replace gcc-runtime libraries & libgcc
#gplv3
#yocto
#llvm
Hello all,
I'm in the process of generating an image without GPLv3 software. I have removed everything but the gcc-runtime and libgcc libraries. These are gpl-3.0 with GCC exception. I'm not sure how
Hello all,
I'm in the process of generating an image without GPLv3 software. I have removed everything but the gcc-runtime and libgcc libraries. These are gpl-3.0 with GCC exception. I'm not sure how
|
By
William Huang
·
#59007
·
|
|
Yocto Project Status 17 January 2023 (WW03)
Current Dev Position: YP 4.2 M2
Next Deadline: 23rd January 2023 YP 4.2 M2 Build
Next Team Meetings:
Bug Triage meeting Thursday January 19th 7:30 am PDT
Current Dev Position: YP 4.2 M2
Next Deadline: 23rd January 2023 YP 4.2 M2 Build
Next Team Meetings:
Bug Triage meeting Thursday January 19th 7:30 am PDT
|
By
Stephen Jolley
·
#59006
·
|
|
Re: gn-native_106.0.5249.119.bb:do_compile failed with exit code '1'
Can you try installing
libstdc++-dev on your build machine ?
Can you try installing
libstdc++-dev on your build machine ?
|
By
Khem Raj
·
#59005
·
|
|
Re: gn-native_106.0.5249.119.bb:do_compile failed with exit code '1'
Is it something about compiler?
Is it something about compiler?
|
By
jovanbosic95@...
·
#59004
·
|
|
gn-native_106.0.5249.119.bb:do_compile failed with exit code '1'
Can someone help me with this problem? I want to install chromium on dunfell, and I am receiving this problem.
jovanbosic@administrator-ThinkPad-L470:~/Yocto/build$ bitbake
Can someone help me with this problem? I want to install chromium on dunfell, and I am receiving this problem.
jovanbosic@administrator-ThinkPad-L470:~/Yocto/build$ bitbake
|
By
jovanbosic95@...
·
#59003
·
|
|
M+ & H bugs with Milestone Movements WW02
All,
YP M+ or high bugs which moved to a new milestone in WW02 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
14960
valgrind ptest fails 12 tests for
All,
YP M+ or high bugs which moved to a new milestone in WW02 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
14960
valgrind ptest fails 12 tests for
|
By
Stephen Jolley
·
#59002
·
|
|
Enhancements/Bugs closed WW02!
All,
The below were the owners of enhancements or bugs closed during the last
All,
The below were the owners of enhancements or bugs closed during the last
|
By
Stephen Jolley
·
#59001
·
|
|
Current high bug count owners for Yocto Project 4.2
All,
Below is the list as of top 34 bug owners as of the end of WW02 of who have open medium or higher bugs and enhancements against YP 4.2. There are 71 possible work days left until the final
All,
Below is the list as of top 34 bug owners as of the end of WW02 of who have open medium or higher bugs and enhancements against YP 4.2. There are 71 possible work days left until the final
|
By
Stephen Jolley
·
#59000
·
|
|
Yocto Project Newcomer & Unassigned Bugs - Help Needed
All,
The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on
All,
The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on
|
By
Stephen Jolley
·
#58999
·
|
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.22.rc1)
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.22.rc1. We are planning to execute following tests for this cycle:
OEQA-manual tests for following module:
1.
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.22.rc1. We are planning to execute following tests for this cycle:
OEQA-manual tests for following module:
1.
|
By
Jing Hui Tham
·
#58998
·
|
|
Re: [meta-security][PATCH] layer.conf: update LAYERSERIES_COMPAT for mickledore
Hi Armin,
can you please merge this to master branch? It's in master-next for a while, but not in master and master-next is missing some changes from master as well, openscap upgrade and kas changes
Hi Armin,
can you please merge this to master branch? It's in master-next for a while, but not in master and master-next is missing some changes from master as well, openscap upgrade and kas changes
|
By
Martin Jansa
·
#58997
·
|
|
Re: [autobuilder][PATCH 0/2] generate regression reports against proper releases
Hi Richard,
Good, I will then add some minor rework to allow introducing unit tests alongside
the version computation in the next revision
OK. I observed a quite similar behaviour while pulling
Hi Richard,
Good, I will then add some minor rework to allow introducing unit tests alongside
the version computation in the next revision
OK. I observed a quite similar behaviour while pulling
|
By
Alexis Lothoré <alexis.lothore@...>
·
#58996
·
|
|
Re: meta-selinux: ERROR: nothing provides coreutils needed by packagegroup-core-selinux
I checked for INCOMPATIBLE_LICENSE FLAG in distro configuration of my image recipe but could not find it. The only place where INCOMPATIBLE_LICENSE is used is in gnutls recipe. I tried using
I checked for INCOMPATIBLE_LICENSE FLAG in distro configuration of my image recipe but could not find it. The only place where INCOMPATIBLE_LICENSE is used is in gnutls recipe. I tried using
|
By
Kamal Kishor
·
#58995
·
|
|
Re: [meta-zephyr][PATCH 1/2][kirkstone] CI: Add variables needed for k8s runners
I ran this series through CI and it passes. See:
https://gitlab.com/jonmason00/meta-zephyr/-/pipelines/747732461
Tested-by: Jon Mason <jon.mason@...>
I ran this series through CI and it passes. See:
https://gitlab.com/jonmason00/meta-zephyr/-/pipelines/747732461
Tested-by: Jon Mason <jon.mason@...>
|
By
Jon Mason
·
#58994
·
|
|
Re: [meta-zephyr][PATCH 1/5][langdale] CI: Add variables needed for k8s runners
I ran this series (batched with the other patches destined for the
langdale branch) through CI and it passes. See:
https://gitlab.com/jonmason00/meta-zephyr/-/pipelines/747805268
Tested-by: Jon
I ran this series (batched with the other patches destined for the
langdale branch) through CI and it passes. See:
https://gitlab.com/jonmason00/meta-zephyr/-/pipelines/747805268
Tested-by: Jon
|
By
Jon Mason
·
#58993
·
|
|
Re: [meta-zephyr][master][langdale][PATCH] zephyr-kernel/3.1: update to latest commit
For master:
I ran this series (batched with the other patches destined for the
master branch) through CI and it passes (with the known qemu a9 poll
issue).
For master:
I ran this series (batched with the other patches destined for the
master branch) through CI and it passes (with the known qemu a9 poll
issue).
|
By
Jon Mason
·
#58992
·
|
|
Re: [meta-zephyr][PATCH] layer.conf: update LAYERSERIES_COMPAT for mickledore
I ran this series (batched with the other patches destined for the
master branch) though CI and it passes (with the known qemu a9 poll
issue).
I ran this series (batched with the other patches destined for the
master branch) though CI and it passes (with the known qemu a9 poll
issue).
|
By
Jon Mason
·
#58991
·
|
|
Re: [meta-zephyr][PATCH 1/5] CI: Add variables needed for k8s runners
I ran this series (batched with the other patches destined for the
master branch) though CI and it passes (with the known qemu a9 poll
issue).
I ran this series (batched with the other patches destined for the
master branch) though CI and it passes (with the known qemu a9 poll
issue).
|
By
Jon Mason
·
#58990
·
|
|
Re: How to properly modify/patch source of a Cargo Crate dependency
<jekefas508=tingn.com@...> wrote:
If you're just patching in later versions of the crates, this should work:
SRC_URI += "crate://crates.io/<target>/<version>"
EXTRA_OECARGO_PATHS =
<jekefas508=tingn.com@...> wrote:
If you're just patching in later versions of the crates, this should work:
SRC_URI += "crate://crates.io/<target>/<version>"
EXTRA_OECARGO_PATHS =
|
By
Alex Kiernan
·
#58989
·
|