|
Re: do_install & RDEPENDS
Alexander Kanavin
It's hard to say what happens if we can't see your recipes. Can you
toggle quoted message
Show quoted text
publish them? Alex On Mon, 15 Aug 2022 at 00:54, Gian Lorenzo Meocci <glmeocci@...> wrote:
|
|
|
|
Re: question about PREFERRED_RPROVIDER
John Wang
I did as Richard suggested, It worked as expected now
feature-public.bb or feature-private.bb: SRC_URI = "git://public or git://private" PROVIDES += "virtual/feature" RPROVIDES:${PN} += " \ virtual-feature \ " machine.conf: PREFERRED_PROVIDER_virtual/feature = "feature-public" Khem Raj <raj.khem@...> 于2022年8月13日周六 22:11写道： No, and I will avoid to use AUTOREV, thank you I checked the yocto-manual, and saw If you use a virtual/\* item with PREFERRED_PROVIDER, then any recipe that PROVIDES that item but is not selected (defined) by PREFERRED_PROVIDER is prevented from building, which is usually desirable since this mechanism is designed to select between mutually exclusive alternative providers[1]. Do you mean if I use AUTOREV, bitbake sill tries to fetch ? And, I am confused about the "PREFERRED_RPROVIDER" , I saw someone use this variable[2], but I cannot find any thing about it In the manual [3] [1] https://docs.yoctoproject.org/ref-manual/variables.html#term-PREFERRED_PROVIDER [2] https://github.com/search?q=PREFERRED_RPROVIDER_virtual&type=code [3] https://docs.yoctoproject.org/genindex.html#P
|
|
|
|
do_install & RDEPENDS
glmeocci@...
Inside the do_install I copy some files but it seems that bitbake set those files in the RDEPENS. In the log during the do_root_fs I see: Requires(post): ... mylib.so After that the commands fail with the error message: Problem: conflicting requests - nothing provides mylib.so needed by mypackage-0.10.14r0.core2_64 Is there a way to disable this behaviour? |
|
|
|
Re: A bitbake error caused by "Variable BB_ENV_EXTRAWHITE"
#bitbake
Alexander Kanavin
Then you need to check the output of 'env'
a) when you start the shell b) when you use oe-init-build-env and figure out how the incorrect variable gets into the environment. Are you using oe-init-build-env from an old yocto? Alex On Sat, 13 Aug 2022 at 15:02, Kaiwan N Billimoria <kaiwan.billimoria@...> wrote: Hello,you probably need to exit the shell and then restart it and |
|
|
|
Re: question about PREFERRED_RPROVIDER
fetcher will try to get versions of recipes during parse phase and if
toggle quoted message
Show quoted text
your recipes are using AUTOREV they will try to poke at git server for latest commit SHA are you using AUTOREV by chance ? On Sat, Aug 13, 2022 at 2:57 AM John Wang <wangzq.jn@...> wrote:
|
|
|
|
[meta-security][PATCH] suricata: fix compile issue
make[2]: *** No rule to make target '../rust/target/arm-poky-linux-gnueabi/release/libsuricata.a', needed by 'suricata'
Signed-off-by: Armin Kuster <akuster808@...> --- recipes-ids/suricata/suricata_6.0.6.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/recipes-ids/suricata/suricata_6.0.6.bb b/recipes-ids/suricata/suricata_6.0.6.bb index 35054ef..efa4bdd 100644 --- a/recipes-ids/suricata/suricata_6.0.6.bb +++ b/recipes-ids/suricata/suricata_6.0.6.bb @@ -145,6 +145,8 @@ export logdir = "${localstatedir}/log" CACHED_CONFIGUREVARS = "ac_cv_func_malloc_0_nonnull=yes ac_cv_func_realloc_0_nonnull=yes" do_configure:prepend () { + # use host for RUST_SURICATA_LIB_XC_DIR + sed -i -e 's:host_alias:host:' ${S}/configure.ac oe_runconf } -- 2.25.1 |
|
|
|
Re: question about PREFERRED_RPROVIDER
Richard Purdie
On Sat, 2022-08-13 at 17:57 +0800, John Wang wrote:
Hi,"virtual" entries only work in PROVIDES and PREFERRED_PROVIDER, not in the runtime version of the variable. Cheers, Richard |
|
|
|
question about PREFERRED_RPROVIDER
John Wang
Hi,
There is a package with two versions, private and public. But when I use the PREFERRED_RPROVIDER to select the public version, bitbake still tries fetch the private one, and then bitabke terminates because do_fetch fails (no permission) What I expect is that when I select the public repository version, it should not fetch the private repository, am I right? Or, should I not use the PREFERRED_RPROVIDER to select a public/private repo ? Could someone guide me :) feature-public.bb ``` SRC_URI = "git://public" RPROVIDES:${PN} += " \ virtual-feature \ " ``` feature-private.bb ``` SRC_URI= "git://private" RPROVIDES:${PN} += " \ virtual-feature \ " ``` machine.conf ``` PREFERRED_RPROVIDER_virtual-feature = "feature-public" ``` |
|
|
|
Re: A bitbake error caused by "Variable BB_ENV_EXTRAWHITE"
#bitbake
Alexander Kanavin
Hello,
toggle quoted message
Show quoted text
you probably need to exit the shell and then restart it and re-initialize your environment (with oe-init-build-env), as it contains the obsolete variable. Alex On Sat, 13 Aug 2022 at 05:13, <lucky33newman@...> wrote:
|
|
|
|
A bitbake error caused by "Variable BB_ENV_EXTRAWHITE"
#bitbake
Yan Xinkuan
Hellow everyone, this is Yan. I am new to Yocto Project, still, I am learning.
There is a question, when I bitbaked my image I found this ERROR: yanxk@yanxk-Ubuntu:~/Yocto/poky/build$ bitbake core-image-sato
ERROR: Variable BB_ENV_EXTRAWHITE has been renamed to BB_ENV_PASSTHROUGH_ADDITIONS
ERROR: Variable BB_ENV_EXTRAWHITE from the shell environment has been renamed to BB_ENV_PASSTHROUGH_ADDITIONS
ERROR: Exiting to allow enviroment variables to be corrected
How can I do a quick fix, and why is it working wrong? By the way, I check the link https://git.openembedded.org/bitbake/commit/?id=87104b6a167188921da157c7dba45938849fb22a , which most likely the main cause. Waiting for a help. |
|
|
|
Re: [meta-security][PATCH] samhain-standalone: fix buildpaths issue
merged
toggle quoted message
Show quoted text
On 8/11/22 02:40, Yu, Mingli wrote:
From: Mingli Yu <mingli.yu@...> |
|
|
|
Re: [meta-security][PATCH V2] meta-security: Add recipe for Glome
merged
toggle quoted message
Show quoted text
On 8/8/22 11:40, John Broadbent via lists.yoctoproject.org wrote:
From: John Edward Broadbent <jebr@...> |
|
|
|
Re: [meta-cgl][PATCH] resource-agents: Bug fix.
Merged.
toggle quoted message
Show quoted text
On 8/7/2022 7:22 PM, leimaohui wrote:
Fix error as the fowllowing: |
|
|
|
Unable to add .bb in a layer - newcomer to Yocto
#yocto
shauli.arazi@...
Hi all,
I have taken on myself a task to write a custom Yocto-based image for Nvidia Xavier which poses somewhat of a difficult task. After few videos on Youtube and some documentation, I started writing a new layer on-top of the tegra and poky layer as follows - meta /home/shauli/Git/poky/meta 5 meta-poky /home/shauli/Git/poky/meta-poky 5 meta-yocto-bsp /home/shauli/Git/poky/meta-yocto-bsp 5 meta-tegra /home/shauli/Git/poky/meta-tegra 5 meta-xtra /home/shauli/Git/poky/meta-xtra 6 meta-xtra is the new layer I wrote that has a .bb file which is supposed to edit the Nvidia logo screen to a custom logo I made. Should be fairly simple. I copied the logo .bb file from the meta-tegra to my own layer under its own folder. meta-xtra/ ├── conf │ └── layer.conf ├── COPYING.MIT ├── README ├── recipes-core │ └── images │ └── xtra-l4t.bb └── recipes-logo ├── xtra-bootlogo │ ├── bootlogo.inc │ ├── files │ │ └── xtra_logo.tar.gz │ └── xtra-bootlogo.bb As can be seen above, I created a new image named xtra-l4t, a logo .bb file which, and the a regular layer.conf file which includes all the .bb files in the subfolders (same as the example). The problem I am facing is that while building either the core-image-base or the xtra-l4t image, the .bb simply doesn't do anything. I had syntax errors in the do_compile () function which I noticed only after compiling the .bb file directly using $ bitbake xtra-bootlogo. The $ bitbake xtra-l4t has no affect whatsoever from the .bb file. I tried adding IMAGE_INSTALL:append = " xtra-bootlogo" to the xtra-l4t.bb file which lead to the following error. ERROR: Task do_populate_sdk in /home/shauli/Git/poky/meta-xtra/recipes-core/images/xtra-l4t.bb rdepends upon non-existent task do_package_write_deb in /home/shauli/Git/poky/meta-xtra/recipes-logo/xtra-bootlogo/xtra-bootlogo.bb I think there is something fundamental about how Yocto works which I fail to understand. This is the logo .bb file - do_compile() { LIST="" if [ "${@bb.utils.contains("PACKAGECONFIG", "raw", "1", "0", d)}" = "1" ]; then if [ ! -s "${S}/${RAW_GRAPHIC_FILE}" ]; then bbfatal "RAW_GRAPHIC_FILE must exist" fi cook_bitmaps "${S}/${RAW_GRAPHIC_FILE}" else if [ ! -s "${S}/${COOKED_CONFIG_FILE}" ]; then bbfatal "COOKED_CONFIG_FILE must exist" fi while read _line do _line="${S}/${_line}" LIST="${LIST}${_line};" done < ${S}/${COOKED_CONFIG_FILE} fi # NB that '%?' gets rid of the trailing ';' because BMP_generator blows up LIST="${LIST%?}" rm -f ${B}/bmp.blob rm -f ${B}/bmp-compressed.blob OUT=${B} ${STAGING_BINDIR_NATIVE}/${FLASHTOOLS_DIR}/BMP_generator_L4T.py -t bmp -e "${LIST}" -v 0 if [ ! -s ${B}/bmp.blob ]; then bbfatal "BMP_generator_L4T.py failed to create bmp.blob" fi compress_blob "${B}/bmp.blob" "${B}/bmp-compressed.blob" if [ ! -s ${B}/bmp-compressed.blob ]; then bbfatal "failed to create compressed bmp-compressed.blob" fi } do_deploy() { install -d ${DEPLOYDIR} install -m 0644 ${B}/bmp-compressed.blob ${DEPLOYDIR}/${BMP_BLOB} # Should overwrite Nvidia's symlink ln -sf ${BMP_BLOB} ${DEPLOYDIR}/${BMP_SYMLINK} } PACKAGE_ARCH = "${MACHINE_ARCH}" do_install[noexec] = "1" addtask deploy before do_build after do_install Any help would be very much appreciated. Thanks, Shauli |
|
|
|
[meta-mingw][PATCH] Switch to HOSTTOOLS_NONFATAL
Joshua Watt
The changes to split classes into global vs. image specific contexts
has broken the inclusion of `wine` and `wineserver` host tools for testing MinGW SDKs. This is because testsdk is an image specific class and therefore it's inclusion is not detected globally and the wine host tools are not present so the SDK tests fail. Resolve this by using HOSTTOOLS_NONFATAL which will include the tools if they exist, but won't fail if they are not present. This does mean that users will now not know they need wine "up front" when doing a build, but it will instead fail later when they actually try to test the SDK, but there isn't really a better way to fix this. Signed-off-by: Joshua Watt <JPEWhacker@...> --- conf/machine-sdk/include/mingw32-common.inc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/conf/machine-sdk/include/mingw32-common.inc b/conf/machine-sdk/include/mingw32-common.inc index 966c63b..07b5b8f 100644 --- a/conf/machine-sdk/include/mingw32-common.inc +++ b/conf/machine-sdk/include/mingw32-common.inc @@ -50,5 +50,4 @@ DISABLE_STATIC:mingw32 = "" GCCPIE:mingw32 = "" # wine and wineserver are required to test MinGW SDKs -HOSTTOOLS += "${@'wine wineserver' if (bb.utils.contains_any('IMAGE_CLASSES', 'testsdk', True, False, d) or any(x in (d.getVar("BBINCLUDED") or "") for x in ["testsdk.bbclass"])) else ''}" - +HOSTTOOLS_NONFATAL += "wine wineserver" -- 2.33.0 |
|
|
|
Re: Remvove unwanted Udev rules
it is part of systemd recipe if your distro is based on systemd. In
toggle quoted message
Show quoted text
that case, you can write a bbappend where you define do_install:append() and delete it from staging area before it gets packaged On Wed, Aug 10, 2022 at 10:59 PM Nikhil Patil <nvpatil2736@...> wrote:
|
|
|
|
Minutes: Yocto Project Weekly Triage Meeting 8/4/2022
sakib.sajal@...
Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Steve Sakoman, Joshua Watt, Randy Macleod,
Richard Purdie, Aryaman, Bruce Ashfield, Michael Opdenacker,
Alexandre Belloni, Pavel Zhukov, Alexandre Belloni, Alejandro
Hernandez, Paulo Neves, Satthishkumar Duraisamy ARs: Notes:
N/A
Medium+ 4.1 Unassigned Enhancements/Bugs: 78 (Last week
78) AB Bugs: 54
(Last week 50)
|
|
|
|
meta-security build failure: suricata
Hello,
I am aware of a new build failure with suricata. I think it related to the glibc update. https://errors.yoctoproject.org/Errors/Build/150774/ I will have limited time to look into this in the next few weeks. - armin |
|
|
|
[meta-security][PATCH] samhain-standalone: fix buildpaths issue
Yu, Mingli
From: Mingli Yu <mingli.yu@...>
Fixes: WARNING: samhain-standalone-4.4.9-r0 do_package_qa: QA Issue: File /usr/share/doc/samhain-standalone/scripts/samhain.ebuild-light in package samhain-standalone-doc contains reference to TMPDIR File /usr/share/doc/samhain-standalone/scripts/samhain.ebuild in package samhain-standalone-doc contains reference to TMPDIR [buildpaths] Signed-off-by: Mingli Yu <mingli.yu@...> --- .../0001-Don-t-expose-configure-args.patch | 44 +++++++++++++++++++ recipes-ids/samhain/samhain-standalone.bb | 1 + 2 files changed, 45 insertions(+) create mode 100644 recipes-ids/samhain/files/0001-Don-t-expose-configure-args.patch diff --git a/recipes-ids/samhain/files/0001-Don-t-expose-configure-args.patch b/recipes-ids/samhain/files/0001-Don-t-expose-configure-args.patch new file mode 100644 index 0000000..fedbe5b --- /dev/null +++ b/recipes-ids/samhain/files/0001-Don-t-expose-configure-args.patch @@ -0,0 +1,44 @@ +From 111b1e8f35e989513d8961a45a806767109f6e1e Mon Sep 17 00:00:00 2001 +From: Mingli Yu <mingli.yu@...> +Date: Thu, 11 Aug 2022 17:15:30 +0800 +Subject: [PATCH] Don't expose configure args + +Don't expost configure args to fix buildpath issue. + +Upstream-Status: Inappropriate [oe specific] + +Signed-off-by: Mingli Yu <mingli.yu@...> +--- + scripts/samhain.ebuild-light.in | 2 +- + scripts/samhain.ebuild.in | 2 +- + 2 files changed, 2 insertions(+), 2 deletions(-) + +diff --git a/scripts/samhain.ebuild-light.in b/scripts/samhain.ebuild-light.in +index 2b09cdb..b7f7062 100644 +--- a/scripts/samhain.ebuild-light.in ++++ b/scripts/samhain.ebuild-light.in +@@ -55,7 +55,7 @@ src_compile() { + # --with-state-dir=/var/lib/${PN} \ + # --with-log-file=/var/log/${PN}.log \ + +- ./configure ${myconf} @mydefargs@ || die ++ ./configure ${myconf} mydefargs || die + emake || die + + echo '#!/bin/sh' > ./sstrip +diff --git a/scripts/samhain.ebuild.in b/scripts/samhain.ebuild.in +index 635a746..b9a42e7 100644 +--- a/scripts/samhain.ebuild.in ++++ b/scripts/samhain.ebuild.in +@@ -55,7 +55,7 @@ src_compile() { + # --with-state-dir=/var/lib/${PN} \ + # --with-log-file=/var/log/${PN}.log \ + +- ./configure ${myconf} @mydefargs@ || die ++ ./configure ${myconf} mydefargs || die + emake || die + + echo '#!/bin/sh' > ./sstrip +-- +2.25.1 + diff --git a/recipes-ids/samhain/samhain-standalone.bb b/recipes-ids/samhain/samhain-standalone.bb index 445cb99..b832dc8 100644 --- a/recipes-ids/samhain/samhain-standalone.bb +++ b/recipes-ids/samhain/samhain-standalone.bb @@ -1,6 +1,7 @@ require samhain.inc SRC_URI += "file://samhain-not-run-ptest-on-host.patch \ + file://0001-Don-t-expose-configure-args.patch \ file://run-ptest \ " -- 2.25.1 |
|
|
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-4.0.3.rc1)
Teoh, Jay Shen
Hello all,
toggle quoted message
Show quoted text
Intel and WR YP QA is planning for QA execution for YP build yocto-4.0.3.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. NUC 7 3. NUC 6 4. Edgerouter 5. Beaglebone ETA for completion next Tuesday, August 16. Thanks, Jay -----Original Message----- |
|
|