|
[WIC] bootimg-partition plugin
A not so well-known feature of the WIC bootimg-partition plugin is that it can install files into different partitions. For that the variable IMAGE_BOOT_FILES has to be defined as one of the following:
IMAGE_BOOT_FILES_label-<partlabel> = "..." IMAGE_BOOT_FILES_uuid-<partuuid> = "..." The plugin will then use either the partition label or the partition uuid from the WKS file "part" directive to look up the correct file list variable. This code snippet from the plugin (poky/scripts/lib/wic/plugins/source/bootimg-partition.py) is supposed to do the trick: 50 boot_files = None 51 for (fmt, id) in (("_uuid-%s", part.uuid), ("_label-%s", part.label), (None, None)): 52 if fmt: 53 var = fmt % id 54 else: 55 var = "" 56 57 print('var: ', var) 58 59 boot_files = get_bitbake_var("IMAGE_BOOT_FILES" + var) 60 if boot_files is not None: 61 break <<<<< However, the function get_bitbake_var() from poky/scripts/lib/wic/misc.py uses the the WIC environment which is created from the WICVARS variable by the poky/meta/classes/image_types_wic.bbclass. WICVARS is defined at the beginning of the class and contains all bitbake variables relevant to WIC. It of course includes the plain IMAGE_BOOT_FILES. When the class creates the environment (do_rootfs_wicenv) is simply splits WICVARS and looks up the variables one-by-one in the DataSmart dictionary (d.getVar(<varname>). Since this is a key lookup it will not match any variables for IMAGE_BOOT_FILES_label-<partlabel> and/or IMAGE_BOOT_FILES_uuid-<partuuid>. For this to work there should be a lookup in DataSmart that supports getVar() with a wildcard or "starts with". I am not all into the details of DataSmart and maybe there is something like this already and I just don't know about it. Hence the question here before I start hacking a kludge into the image_types_wic class. Thanks, Rudi -- Rudolf J Streif CEO/CTO ibeeto +1.855.442.3386 x700
|
|
|
|
Re: googletest shared library
Lijun Chen
Tried adding googletest to TOOLCHAIN_TARGET_TASK. The gtest .h files are still not showing up. Thanks,
From: Khem Raj <raj.khem@...>
Sent: Wednesday, September 22, 2021 11:28:05 AM To: Lijun Chen; yocto@... Subject: Re: [yocto] googletest shared library The .h files will be in dev pkg in this case googletest-dev
what happens if you add googletest to TOOLCHAIN_TARGET_TASK On 9/22/21 6:18 AM, Lijun Chen wrote: > Hi, > > > Now I included googletest to the IMAGE_INSTALL in my image file, and > built both board image and SDK image. I can see libgtest.so is available > in both images. However, gtest/gtest.h is a not present in SDK. How do I > add the header files to the SDK image? Looks the following lines affect > that? > > SOLIBS = ".so" > FILES_SOLIBSDEV = "" > > Thanks, > Lijun > > ------------------------------------------------------------------------ > *From:* yocto@... <yocto@...> on > behalf of Lijun Chen <lijchen@...> > *Sent:* Tuesday, September 21, 2021 3:50 PM > *To:* Konrad Weihmann; yocto@... > *Subject:* Re: [yocto] googletest shared library > > Thanks Konrad. That worked. > > ------------------------------------------------------------------------ > *From:* Konrad Weihmann <kweihmann@...> > *Sent:* Tuesday, September 21, 2021 10:26:19 AM > *To:* Lijun Chen; yocto@... > *Subject:* Re: [yocto] googletest shared library > > On 21.09.21 16:18, Lijun Chen wrote: >> Hi, >> >> I would like to include libgtest.so into my Yocto image. I added >> googletest to IMAGE_INSTALL and added the following line to >> sources/meta-openembedded/meta-oe/recipes-test/googletest/googletest_git.bb: >> >> EXTRA_OECMAKE = "-DBUILD_SHARED_LIBS=ON " >> >> >> The shared libraries were built successfully. However, there are errors >> in do_package_qc as following: >> >> >> ERROR: googletest-1.10.0-r0 do_package_qa: QA Issue: -dev package >> googletest-dev contains non-symlink .so '/usr/lib/libgmock.so' >> -dev package googletest-dev contains non-symlink .so >> '/usr/lib/libgtest_main.so' >> -dev package googletest-dev contains non-symlink .so >> '/usr/lib/libgmock_main.so' >> -dev package googletest-dev contains non-symlink .so >> '/usr/lib/libgtest.so' [dev-elf] >> ERROR: googletest-1.10.0-r0 do_package_qa: QA run found fatal errors. >> Please consider fixing them. > > https://urldefense.com/v3/__http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-graphics/spir/spirv-tools_2021.2.bb*n34__;Iw!!COg3wY07Hnb7!4NI6d6tXUoxCQFleF-343dfbdFGnkZnqrYRVg3nYTCBoGJTY9-K0NANM4iMsNNleww$ > <https://urldefense.com/v3/__http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-graphics/spir/spirv-tools_2021.2.bb*n34__;Iw!!COg3wY07Hnb7!4NI6d6tXUoxCQFleF-343dfbdFGnkZnqrYRVg3nYTCBoGJTY9-K0NANM4iMsNNleww$> > > (and the next lines) might give you a hint what to do in this case. > Although one could also consider that's something that needs to be fixed > in the installation script of googletest, as versioned libraries are the > expected default > >> >> >> Any idea to fix this? >> >> >> Thanks, >> >> Lijun >> >> >> ------------------------------------------------------------------------ >> This transmission (including any attachments) may contain confidential >> information, privileged material (including material protected by the >> solicitor-client or other applicable privileges), or constitute >> non-public information. Any use of this information by anyone other than >> the intended recipient is prohibited. If you have received this >> transmission in error, please immediately reply to the sender and delete >> this information from your system. Use, dissemination, distribution, or >> reproduction of this transmission by unintended recipients is not >> authorized and may be unlawful. >> >> >> >> > ------------------------------------------------------------------------ > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute > non-public information. Any use of this information by anyone other than > the intended recipient is prohibited. If you have received this > transmission in error, please immediately reply to the sender and delete > this information from your system. Use, dissemination, distribution, or > reproduction of this transmission by unintended recipients is not > authorized and may be unlawful. > ------------------------------------------------------------------------ > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute > non-public information. Any use of this information by anyone other than > the intended recipient is prohibited. If you have received this > transmission in error, please immediately reply to the sender and delete > this information from your system. Use, dissemination, distribution, or > reproduction of this transmission by unintended recipients is not > authorized and may be unlawful. > > > > This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
|
|
|
|
Re: Permission denied with NFS shared download and sstate-cache
Richard Purdie
On Wed, 2021-09-22 at 09:51 -0700, Khem Raj wrote:
On Wed, Sep 22, 2021 at 9:47 AM Bel Hadj Salem Talel <bhstalel@...> wrote:The file is being created with python's tempfile function which will make itits trying to create the file with 0600 mask. I wonder whats your secure. Secure in this context means 00600... I suspect you're right that creating a file securely here with this permissions likely can't work. Cheers, Richard
|
|
|
|
[PATCH yocto-autobuilder-helper] scripts/collect-results: publish everything in tmp/log/oeqa
Alexander Kanavin
From: Alexander Kanavin <alex@...>
In addition to the testresult json, testimage class now also provides task logs and qemu console output (splitted into folders by image name to avoid clutter), which can be useful for debugging test failures or even checking qemu test runs when failures did not happen. Rather than duplicate specific file/folder names, let's copy all that is available, and define what is published in the testimage class itself. [YOCTO #14518] Signed-off-by: Alexander Kanavin <alex@...> Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- scripts/collect-results | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/scripts/collect-results b/scripts/collect-results index 93834d6..3663330 100755 --- a/scripts/collect-results +++ b/scripts/collect-results @@ -3,11 +3,9 @@ WORKDIR=$1 DEST=$2 target=$3 -RESFILE=$WORKDIR/tmp/log/oeqa/testresults.json - -if [ -e $RESFILE ]; then - mkdir -p $DEST/$target - cp $WORKDIR/tmp/log/oeqa/testresults.json $DEST/$target/ +mkdir -p $DEST +if [ -e $WORKDIR/tmp/log/oeqa/ ]; then + cp -rf $WORKDIR/tmp/log/oeqa/ $DEST/$target fi if [ -e $WORKDIR/buildhistory ]; then -- 2.31.1
|
|
|
|
Re: Permission denied with NFS shared download and sstate-cache
On Wed, Sep 22, 2021 at 9:47 AM Bel Hadj Salem Talel <bhstalel@...> wrote:
its trying to create the file with 0600 mask. I wonder whats your global umask set to. and perhaps the user is not same when bitbake it running ? PermissionError: [Errno 13] Permission denied: '/home/talel/Desktop/YoctoShare/tethys-cache/ubuntu-20.04/dd/sigtask.dgjx7ngq'
|
|
|
|
Permission denied with NFS shared download and sstate-cache
Bel Hadj Salem Talel <bhstalel@...>
Hi All,
I have a server that's holding downloads and sstate-cache. I have a docker-compose file with nfs server that exposes the dowloads/sstate-cache volume. When I mount that in my PC and set the path into DL_DIR and SSTATE_DIR, I get this error : --------------- ERROR: grub-efi-native-2.04-r0 do_configure: Build of do_configure failed ERROR: grub-efi-native-2.04-r0 do_configure: Traceback (most recent call last): File "/home/talel/Desktop/YoctoWork/sources/poky/bitbake/lib/bb/build.py", line 644, in exec_task return _exec_task(fn, task, d, quieterr) File "/home/talel/Desktop/YoctoWork/sources/poky/bitbake/lib/bb/build.py", line 618, in _exec_task event.fire(TaskSucceeded(task, fn, logfn, localdata), localdata) File "/home/talel/Desktop/YoctoWork/sources/poky/bitbake/lib/bb/event.py", line 215, in fire fire_class_handlers(event, d) File "/home/talel/Desktop/YoctoWork/sources/poky/bitbake/lib/bb/event.py", line 122, in fire_class_handlers execute_handler(name, handler, event, d) File "/home/talel/Desktop/YoctoWork/sources/poky/bitbake/lib/bb/event.py", line 94, in execute_handler ret = handler(event) File "/home/talel/Desktop/YoctoWork/sources/poky/meta/classes/sstate.bbclass", line 1094, in sstate_eventhandler bb.siggen.dump_this_task(sstatepkg + '_' + taskname + ".tgz" ".siginfo", d) File "/home/talel/Desktop/YoctoWork/sources/poky/bitbake/lib/bb/siggen.py", line 648, in dump_this_task bb.parse.siggen.dump_sigtask(fn, task, outfile, "customfile:" + referencestamp) File "/home/talel/Desktop/YoctoWork/sources/poky/meta/lib/oe/sstatesig.py", line 202, in dump_sigtask super(bb.siggen.SignatureGeneratorBasicHash, self).dump_sigtask(fn, task, stampbase, runtime) File "/home/talel/Desktop/YoctoWork/sources/poky/bitbake/lib/bb/siggen.py", line 362, in dump_sigtask fd, tmpfile = tempfile.mkstemp(dir=os.path.dirname(sigfile), prefix="sigtask.") File "/usr/lib/python3.8/tempfile.py", line 470, in mkstemp return _mkstemp_inner(dir, prefix, suffix, flags, output_type) File "/usr/lib/python3.8/tempfile.py", line 389, in _mkstemp_inner fd = _os.open(file, flags, 0o600) PermissionError: [Errno 13] Permission denied: '/home/talel/Desktop/YoctoShare/tethys-cache/ubuntu-20.04/dd/sigtask.dgjx7ngq' ERROR: Task (virtual:native:/home/talel/Desktop/YoctoWork/sources/poky/meta/recipes-bsp/grub/grub-efi_2.04.bb:do_configure) failed with exit code '1' --------------- I can modify the mounted folder by creating a directory or a file, but it fails with yocto. How can I solve the issue? Thanks, Talel
|
|
|
|
Re: googletest shared library
The .h files will be in dev pkg in this case googletest-dev
toggle quoted messageShow quoted text
what happens if you add googletest to TOOLCHAIN_TARGET_TASK
On 9/22/21 6:18 AM, Lijun Chen wrote:
Hi,
|
|
|
|
[PATCH][dunfell] config.json: Ensure BB_HASHSERVE is set in SDKs to auto
Steve Sakoman
From: Richard Purdie <richard.purdie@...>
Signed-off-by: Richard Purdie <richard.purdie@...> (cherry picked from commit 4689763b513521fc70cca576b88035de240a3ba6) Signed-off-by: Steve Sakoman <steve@...> --- config.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config.json b/config.json index 571ddae..fa475e3 100644 --- a/config.json +++ b/config.json @@ -31,7 +31,7 @@ "DLDIR" : "DL_DIR = '${BASE_SHAREDDIR}/current_sources'", "SSTATEDIR" : ["SSTATE_DIR ?= '${BASE_SHAREDDIR}/pub/sstate-dunfell'"], "SSTATEDIR_RELEASE" : ["SSTATE_MIRRORS += 'file://.* file://${BASE_SHAREDDIR}/pub/sstate-dunfell/PATH'", "SSTATE_DIR ?= '${BASE_PUBLISHDIR}/sstate/@RELEASENUM@'"], - "SDKEXTRAS" : ["SSTATE_MIRRORS += '\\", "file://.* http://sstate.yoctoproject.org/dev/@RELEASENUM@PATH;downloadfilename=PATH'"], + "SDKEXTRAS" : ["SSTATE_MIRRORS += '\\", "file://.* http://sstate.yoctoproject.org/dev/@RELEASENUM@PATH;downloadfilename=PATH'", "BB_HASHSERVE = 'auto'"], "BUILDINFO" : false, "BUILDHISTORY" : false, "BUILDINFOVARS" : ["INHERIT += 'image-buildinfo'", "IMAGE_BUILDINFO_VARS_append = ' IMAGE_BASENAME IMAGE_NAME'"], -- 2.25.1
|
|
|
|
Re: googletest shared library
Lijun Chen
Hi,
Now I included googletest to the IMAGE_INSTALL in my image file, and built both board image and SDK image. I can see libgtest.so is available in both images. However, gtest/gtest.h is a not present in SDK. How do I add the header files to the
SDK image? Looks the following lines affect that? SOLIBS = ".so"
FILES_SOLIBSDEV = ""
Thanks,
Lijun
From: yocto@... <yocto@...> on behalf of Lijun Chen <lijchen@...>
Sent: Tuesday, September 21, 2021 3:50 PM To: Konrad Weihmann; yocto@... Subject: Re: [yocto] googletest shared library Thanks Konrad. That worked. From: Konrad Weihmann <kweihmann@...>
Sent: Tuesday, September 21, 2021 10:26:19 AM To: Lijun Chen; yocto@... Subject: Re: [yocto] googletest shared library On 21.09.21 16:18, Lijun Chen wrote: > Hi, > > I would like to include libgtest.so into my Yocto image. I added > googletest to IMAGE_INSTALL and added the following line to > sources/meta-openembedded/meta-oe/recipes-test/googletest/googletest_git.bb: > > EXTRA_OECMAKE = "-DBUILD_SHARED_LIBS=ON " > > > The shared libraries were built successfully. However, there are errors > in do_package_qc as following: > > > ERROR: googletest-1.10.0-r0 do_package_qa: QA Issue: -dev package > googletest-dev contains non-symlink .so '/usr/lib/libgmock.so' > -dev package googletest-dev contains non-symlink .so > '/usr/lib/libgtest_main.so' > -dev package googletest-dev contains non-symlink .so > '/usr/lib/libgmock_main.so' > -dev package googletest-dev contains non-symlink .so > '/usr/lib/libgtest.so' [dev-elf] > ERROR: googletest-1.10.0-r0 do_package_qa: QA run found fatal errors. > Please consider fixing them. https://urldefense.com/v3/__http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-graphics/spir/spirv-tools_2021.2.bb*n34__;Iw!!COg3wY07Hnb7!4NI6d6tXUoxCQFleF-343dfbdFGnkZnqrYRVg3nYTCBoGJTY9-K0NANM4iMsNNleww$ (and the next lines) might give you a hint what to do in this case. Although one could also consider that's something that needs to be fixed in the installation script of googletest, as versioned libraries are the expected default > > > Any idea to fix this? > > > Thanks, > > Lijun > > > ------------------------------------------------------------------------ > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute > non-public information. Any use of this information by anyone other than > the intended recipient is prohibited. If you have received this > transmission in error, please immediately reply to the sender and delete > this information from your system. Use, dissemination, distribution, or > reproduction of this transmission by unintended recipients is not > authorized and may be unlawful. > > > > This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
|
|
|
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.11.rc2)
Teoh, Jay Shen
Hi all,
toggle quoted messageShow quoted text
This is the full report for yocto-3.1.11.rc2: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high milestone defects. 1 new issue found BUG id:14557 - oe_syslog.SyslogTestConfig.test_syslog_startup_config failure ======= Bugs ======== https://bugzilla.yoctoproject.org/show_bug.cgi?id=14557 Thanks, Jay
-----Original Message-----
|
|
|
|
Re: Switch to a different Python3 version
Richard Purdie
On Tue, 2021-09-21 at 20:00 +0000, Lijun Chen wrote:
Hi,Hard to say without understanding how it failed. What was the error? You probably need to match python3 and python3-native versions but I don't know if you did. Cheers, Richard
|
|
|
|
Re: Switch to a different Python3 version
Alexander Kanavin
The best way is to fix the app. Such major downgrades are firmly uncharted territory, and aren't supported. If you have errors, you need to figure out yourself how to fix them - but if you provide the logs, we can try to help. Alex
On Tue, 21 Sept 2021 at 22:00, Lijun Chen <lijchen@...> wrote:
|
|
|
|
Switch to a different Python3 version
Lijun Chen
Hi,
Currently we are building a Yocto image based on Hardknott release, which includes python 3.9.4. Due to a App constraint, we have to downgrade Python3 to 3.8. I tried copying over 3.8.5 bb file and associated poky/meta/recipes-devtools/python/python3/ folder, but the building failed. What is the best way to switch/downgrade python3 version?
Thanks, Lijun This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
|
|
|
|
Re: googletest shared library
Lijun Chen
Thanks Konrad. That worked.
From: Konrad Weihmann <kweihmann@...>
Sent: Tuesday, September 21, 2021 10:26:19 AM To: Lijun Chen; yocto@... Subject: Re: [yocto] googletest shared library On 21.09.21 16:18, Lijun Chen wrote: > Hi, > > I would like to include libgtest.so into my Yocto image. I added > googletest to IMAGE_INSTALL and added the following line to > sources/meta-openembedded/meta-oe/recipes-test/googletest/googletest_git.bb: > > EXTRA_OECMAKE = "-DBUILD_SHARED_LIBS=ON " > > > The shared libraries were built successfully. However, there are errors > in do_package_qc as following: > > > ERROR: googletest-1.10.0-r0 do_package_qa: QA Issue: -dev package > googletest-dev contains non-symlink .so '/usr/lib/libgmock.so' > -dev package googletest-dev contains non-symlink .so > '/usr/lib/libgtest_main.so' > -dev package googletest-dev contains non-symlink .so > '/usr/lib/libgmock_main.so' > -dev package googletest-dev contains non-symlink .so > '/usr/lib/libgtest.so' [dev-elf] > ERROR: googletest-1.10.0-r0 do_package_qa: QA run found fatal errors. > Please consider fixing them. https://urldefense.com/v3/__http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-graphics/spir/spirv-tools_2021.2.bb*n34__;Iw!!COg3wY07Hnb7!4NI6d6tXUoxCQFleF-343dfbdFGnkZnqrYRVg3nYTCBoGJTY9-K0NANM4iMsNNleww$ (and the next lines) might give you a hint what to do in this case. Although one could also consider that's something that needs to be fixed in the installation script of googletest, as versioned libraries are the expected default > > > Any idea to fix this? > > > Thanks, > > Lijun > > > ------------------------------------------------------------------------ > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute > non-public information. Any use of this information by anyone other than > the intended recipient is prohibited. If you have received this > transmission in error, please immediately reply to the sender and delete > this information from your system. Use, dissemination, distribution, or > reproduction of this transmission by unintended recipients is not > authorized and may be unlawful. > > > > This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
|
|
|
|
Yocto Project Status WW38`21
Stephen Jolley
Current Dev Position: YP 3.4 M4 Next Deadline: 4th Oct. 2021 YP 3.4 M4 build
Next Team Meetings:
Key Status/Updates:
Ways to contribute:
YP 3.4 Milestone Dates:
Planned upcoming dot releases:
Tracking Metrics:
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
|
|
|
Re: googletest shared library
Konrad Weihmann <kweihmann@...>
On 21.09.21 16:18, Lijun Chen wrote:
Hi,http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-graphics/spir/spirv-tools_2021.2.bb#n34 (and the next lines) might give you a hint what to do in this case. Although one could also consider that's something that needs to be fixed in the installation script of googletest, as versioned libraries are the expected default Any idea to fix this?
|
|
|
|
googletest shared library
Lijun Chen
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
|
|
|
|
[yocto-autobuilder-helper][dunfell] config.json: Add BB_HASHSERVE to SDK_LOCAL_CONF_BLACKLIST
Steve Sakoman
From: Richard Purdie <richard.purdie@...>
This should avoid issues with the hashequiv code attempting to contact an non-existent server in the eSDKs built by the project. [YOCTO #14471] Signed-off-by: Richard Purdie <richard.purdie@...> (cherry picked from commit 4db17f4c9da4efb48d428256efb696d86935a3ea) Signed-off-by: Steve Sakoman <steve@...> --- config.json | 1 + 1 file changed, 1 insertion(+) diff --git a/config.json b/config.json index d871349..571ddae 100644 --- a/config.json +++ b/config.json @@ -55,6 +55,7 @@ "SANITY_TESTED_DISTROS = ''", "SDK_EXT_TYPE = 'minimal'", "SDK_INCLUDE_TOOLCHAIN = '1'", + "SDK_LOCAL_CONF_BLACKLIST:append = 'BB_HASHSERVE'", "BB_DISKMON_DIRS = 'STOPTASKS,${TMPDIR},1G,100K STOPTASKS,${DL_DIR},1G STOPTASKS,${SSTATE_DIR},1G STOPTASKS,/tmp,100M,100K ABORT,${TMPDIR},100M,1K ABORT,${DL_DIR},100M ABORT,${SSTATE_DIR},100M ABORT,/tmp,10M,1K'", "BB_HASHSERVE = 'typhoon.yocto.io:8686'" ] -- 2.25.1
|
|
|
|
[hardknott][meta-yocto][PATCH 4/4] yocto-bsp/5.10: update to v5.10.63
Anuj Mittal
From: Bruce Ashfield <bruce.ashfield@...>
Updating the reference platforms to match the latest 5.10 -stable in oe-core. Signed-off-by: Bruce Ashfield <bruce.ashfield@...> Signed-off-by: Richard Purdie <richard.purdie@...> (cherry picked from commit 77b8e31f706cb29d1efb19305470d9b525fc5a67) Signed-off-by: Anuj Mittal <anuj.mittal@...> --- .../linux/linux-yocto_5.10.bbappend | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.10.bbappend b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.10.bbappend index 0e5e3b1..347a411 100644 --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.10.bbappend +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.10.bbappend @@ -7,17 +7,17 @@ KMACHINE_genericx86 ?= "common-pc" KMACHINE_genericx86-64 ?= "common-pc-64" KMACHINE_beaglebone-yocto ?= "beaglebone" -SRCREV_machine_genericx86 ?= "c274623910704eefcc98380a17649889ac7e9408" -SRCREV_machine_genericx86-64 ?= "c274623910704eefcc98380a17649889ac7e9408" -SRCREV_machine_edgerouter ?= "ac089d661362ba857e235c5630242039b150ae26" -SRCREV_machine_beaglebone-yocto ?= "a6df693a45f5787d4254e0998f52b4465b2a5efe" +SRCREV_machine_genericx86 ?= "164ed895bc1e94722e80fe6496b176f6bb815cd4" +SRCREV_machine_genericx86-64 ?= "164ed895bc1e94722e80fe6496b176f6bb815cd4" +SRCREV_machine_edgerouter ?= "4ab94e777d8b41ee1ee4c279259e9733bc8049b1" +SRCREV_machine_beaglebone-yocto ?= "941cc9c3849f96f7eaf109b1e35e05ba366aca56" COMPATIBLE_MACHINE_genericx86 = "genericx86" COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64" COMPATIBLE_MACHINE_edgerouter = "edgerouter" COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto" -LINUX_VERSION_genericx86 = "5.10.55" -LINUX_VERSION_genericx86-64 = "5.10.55" -LINUX_VERSION_edgerouter = "5.10.55" -LINUX_VERSION_beaglebone-yocto = "5.10.55" +LINUX_VERSION_genericx86 = "5.10.63" +LINUX_VERSION_genericx86-64 = "5.10.63" +LINUX_VERSION_edgerouter = "5.10.63" +LINUX_VERSION_beaglebone-yocto = "5.10.63" -- 2.31.1
|
|
|
|
[hardknott][meta-yocto][PATCH 3/4] meta-yocto-bsp: Bump to the v5.10.55
Anuj Mittal
From: Kevin Hao <kexin.hao@...>
Build and boot test for all the boards. Signed-off-by: Kevin Hao <kexin.hao@...> Signed-off-by: Richard Purdie <richard.purdie@...> (cherry picked from commit 8b5c126510dbf265dc494ff7c8decbae63f5b597) Signed-off-by: Anuj Mittal <anuj.mittal@...> --- .../linux/linux-yocto_5.10.bbappend | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.10.bbappend b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.10.bbappend index f8362b6..0e5e3b1 100644 --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.10.bbappend +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.10.bbappend @@ -7,17 +7,17 @@ KMACHINE_genericx86 ?= "common-pc" KMACHINE_genericx86-64 ?= "common-pc-64" KMACHINE_beaglebone-yocto ?= "beaglebone" -SRCREV_machine_genericx86 ?= "ab49d2db98bdee2c8c6e17fb59ded9e5292b0f41" -SRCREV_machine_genericx86-64 ?= "ab49d2db98bdee2c8c6e17fb59ded9e5292b0f41" -SRCREV_machine_edgerouter ?= "274d63799465eebfd201b3e8251f16d29e93a978" -SRCREV_machine_beaglebone-yocto ?= "ab49d2db98bdee2c8c6e17fb59ded9e5292b0f41" +SRCREV_machine_genericx86 ?= "c274623910704eefcc98380a17649889ac7e9408" +SRCREV_machine_genericx86-64 ?= "c274623910704eefcc98380a17649889ac7e9408" +SRCREV_machine_edgerouter ?= "ac089d661362ba857e235c5630242039b150ae26" +SRCREV_machine_beaglebone-yocto ?= "a6df693a45f5787d4254e0998f52b4465b2a5efe" COMPATIBLE_MACHINE_genericx86 = "genericx86" COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64" COMPATIBLE_MACHINE_edgerouter = "edgerouter" COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto" -LINUX_VERSION_genericx86 = "5.10.43" -LINUX_VERSION_genericx86-64 = "5.10.43" -LINUX_VERSION_edgerouter = "5.10.43" -LINUX_VERSION_beaglebone-yocto = "5.10.43" +LINUX_VERSION_genericx86 = "5.10.55" +LINUX_VERSION_genericx86-64 = "5.10.55" +LINUX_VERSION_edgerouter = "5.10.55" +LINUX_VERSION_beaglebone-yocto = "5.10.55" -- 2.31.1
|
|
|