Date   

Re: How to remove Kernel headers from SDK

Khem Raj
 

On 11/13/20 5:20 AM, Bel Hadj Salem Talel wrote:
Hi All,
I need to deliver an SDK for arch64 but without Kernel headers that one can build Kernel modules with them. (/usr/include/linux/* , ...)
I only need to deliver an SDK with toolchain and minimal headers for compilation such as "stdio.h" , ...
How can I do it ?

perhaps bitbak meta-toolchain would suffice

Thanks, Talel


How to remove Kernel headers from SDK

Bel Hadj Salem Talel
 

Hi All,
I need to deliver an SDK for arch64 but without Kernel headers that one can build Kernel modules with them. (/usr/include/linux/* , ...)
I only need to deliver an SDK with toolchain and minimal headers for compilation such as "stdio.h" , ...

How can I do it ?
Thanks, Talel


Re: Trying to compile hping3 from sources #devtool

Khem Raj
 

Hey Manasa !!

Long time, happy to hear from you. I hope you are doing well,

Hi Vaijayanthi

I took a look at hping3 and its one package thats not cross-compile
friendly, So no wonder Vaijayanthi was finding all sorts of issues.
It was looking at host system for tcl and all kind of other headers
which was causing the issues you were seeing.

Just for Manasa I gave it a whirl :) and here is a version which should
work (At least it compiles), its completely untested but I hope it will
unblock you

https://github.com/YoeDistro/meta-openembedded/commit/c4a5be527f61f286cd47352f56b563390a4e3d58

You can download this

curl -O
https://github.com/YoeDistro/meta-openembedded/commit/c4a5be527f61f286cd47352f56b563390a4e3d58.patch

cd meta-openembedded

git am c4a5be527f61f286cd47352f56b563390a4e3d58.patch

then

bitbake hping3

Let me know if it is helpful

Thank you

-Khem

On 11/12/20 12:59 PM, Godavarthi, Manasa wrote:
Hi Raj,

 

Small world! Hope you are doing well. I would love to catch up sometime
with you.

 

Vaijayanthi also worked with me at Juniper. We really appreciate your
help regarding hping3. Basically, there is no recipe for hping3, looks
like. So, Vaijayanthi is trying to compile from source and include it as
part of our Yocto build and SDK so that hping3 binary is available as
part of our linux distro.

 

Regards,

--Manasa

 

*From: *Muralidharan, Vaijayanthi <vaijayanthi.muralidharan@hpe.com>
*Date: *Thursday, November 12, 2020 at 12:36 PM
*To: *raj.khem@gmail.com <raj.khem@gmail.com>
*Cc: *Vaijayanthi <vaijayanthi@silver-peak.com>, Yocto-mailing-list
<yocto@lists.yoctoproject.org>, Godavarthi, Manasa
<manasa.godavarthi@hpe.com>
*Subject: *Re: [yocto] Trying to compile hping3 from sources #devtool

Just to add more to this: I managed to build via bitbake successfully.
But "make" fails with the following error:
Problem: package packagegroup-sps-all-1.0-r0.noarch requires
packagegroup-sps-network-utils, but none of the providers can be installed
  - package packagegroup-sps-network-utils-1.0-r0.noarch requires
hping3, but none of the providers can be installed
  - conflicting requests
  - nothing provides libpcap.so.0.8()(64bit) needed by
hping3-git-r0.core2_64
  - nothing provides libtcl8.6.so()(64bit) needed by hping3-git-r0.core2_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest'
to use not only best candidate packages)

ERROR: sps-image-vxoa-1.0-r0 do_rootfs:

I have added RDENPDS for libpcap and libtcl in hping3's recipe.

On 11/9/20, 4:06 PM, "Muralidharan, Vaijayanthi"
<vaijayanthi.muralidharan@hpe.com> wrote:

    This is a recipe that was created via devtool.

    devtool add hping3 https://github.com/antirez/hping

    On 11/9/20, 10:43 AM, "Muralidharan, Vaijayanthi"
<vaijayanthi.muralidharan@hpe.com> wrote:

        hping3_git.bb

        On 11/7/20, 12:04 PM, "yocto@lists.yoctoproject.org on behalf of
Khem Raj via lists.yoctoproject.org" <yocto@lists.yoctoproject.org on
behalf of raj.khem=gmail.com@lists.yoctoproject.org> wrote:

            On Sat, Nov 7, 2020 at 11:57 AM Muralidharan, Vaijayanthi
            <vaijayanthi.muralidharan@hpe.com> wrote:
            >
            > Khem,
            >
            > Thanks for responding. I am trying to build hping3 from
sources. There is only a bb recipe for hping2.
            >

            what is your failing recipe called (exact name )

            > On 11/6/20, 9:42 PM, "Khem Raj" <raj.khem@gmail.com> wrote:
            >
            >     whats the name of your recipe ? secondly hping3
requires libtcl8.6.so
            >     seems to be troublesome because its asking
            >     for devel package not the original library, I wonder
why, can you find
            >     out the linker cmdline where ping3 is getting linked ?
            >
            >     On Fri, Nov 6, 2020 at 6:31 PM Vaijayanthi
<vaijayanthi@silver-peak.com> wrote:
            >     >
            >     > Hi, I am using devtool add hping3
https://github.com/antirez/hping to add hping3 as part of our custom
image. Here is my recipe:
            >     >
            >     > # Recipe created by recipetool
            >     >
            >     > # This is the basis of a recipe and may need further
editing in order to be fully functional.
            >     >
            >     > # (Feel free to remove these comments when editing.)
            >     >
            >     >
            >     >
            >     > # WARNING: the following LICENSE and
LIC_FILES_CHKSUM values are best guesses - it is
            >     >
            >     > # your responsibility to verify that the values are
complete and correct.
            >     >
            >     > #
            >     >
            >     > # The following license files were not able to be
identified and are
            >     >
            >     > # represented as "Unknown" below, you will need to
check them yourself:
            >     >
            >     > #   COPYING
            >     >
            >     > LICENSE = "GPLv2"
            >     >
            >     > LIC_FILES_CHKSUM =
"file://COPYING;md5=3728a6c4c9630a9e796ad4b82dacd887
<file:///COPYING;md5=3728a6c4c9630a9e796ad4b82dacd887>"
            >     >
            >     >
            >     >
            >     > SRC_URI =
"git://github.com/antirez/hping;protocol=https"
            >     >
            >     >
            >     >
            >     > # Modify these as desired
            >     >
            >     > PV = "1.0+git${SRCPV}"
            >     >
            >     > SRCREV = "3547c7691742c6eaa31f8402e0ccbb81387c1b99"
            >     >
            >     >
            >     >
            >     > S = "${WORKDIR}/git"
            >     >
            >     >
            >     >
            >     > #DEPENDS = "libpcap"
            >     >
            >     > RDEPENDS_${PN} += " libpcap tcl-lib tcl"
            >     >
            >     >
            >     >
            >     > # NOTE: no Makefile found, unable to determine what
needs to be done
            >     >
            >     >
            >     >
            >     > do_configure () {
            >     >
            >     >     # Specify any needed configure commands here
            >     >
            >     >     CONFIGOSTYPE="LINUX" ./configure
            >     >
            >     > }
            >     >
            >     >
            >     >
            >     > do_compile () {
            >     >
            >     >     # Specify compilation commands here
            >     >
            >     >     make
            >     >
            >     > }
            >     >
            >     > do_install() {
            >     >
            >     >     #install -Dm755 ${B}/libpcap.so.0.8
${D}${libdir}/libpcap.so.0.8
            >     >
            >     >     #ln -sf libpcap.so.0.8 ${D}${libdir}/libpcap.so
            >     >
            >     >     #install -Dm755 ${B}/libtcl8.6.so
${D}${libdir}/libtcl8.6.so
            >     >
            >     >     #ln -sf libtcl8.6.so ${D}${libdir}/libtcl8.6.so
            >     >
            >     >     install -m 0755 -d ${D}${sbindir} ${D}/${mandir}
${D}${docdir}/hping3
            >     >
            >     >     install -m 0755 hping3 ${D}/${sbindir}
            >     >
            >     >     install -m 0644 docs/hping3.8 ${D}/${mandir}
            >     >
            >     >     install -m 0644 docs/HPING2-HOWTO.txt
docs/HPING2-IS-OPEN \
            >     >
            >     >         docs/MORE-FUN-WITH-IPID docs/SPOOFED_SCAN.txt \
            >     >
            >     >         docs/AS-BACKDOOR docs/APD.txt
${D}${docdir}/hping3
            >     >
            >     > }
            >     >
            >     >
            >     >
            >     > #INSANE_SKIP_${PN}-dev = "ldflags"
            >     >
            >     > #INSANE_SKIP_${PN} = "ldflags"
            >     >
            >     > #INSANE_SKIP_${PN} += "file-rdeps dev-deps"
            >     >
            >     >
            >     > How do I add this to my custom bitbake layer? Also,
make is complaining about
            >     > ERROR: hping3-1.0+git999-r0 do_package_qa: QA Issue:
/usr/sbin/hping3 contained in package hping3 requires
libpcap.so.0.8()(64bit), but no providers found in RDEPENDS_hping3?
[file-rdeps]
            >     > ERROR: hping3-1.0+git999-r0 do_package_qa: QA Issue:
/usr/sbin/hping3 contained in package hping3 requires
libtcl8.6.so()(64bit), but no providers found in RDEPENDS_hping3?
[file-rdeps]
            >     > ERROR: hping3-1.0+git999-r0 do_package_qa: QA run
found fatal errors. Please consider fixing them.
            >     >
            >     > Please let me know what I should I do next to
integrate this recipe with my custom meta layer and also, address the
make failures.
            >     >
            >     >
            >     >
            >     >
            >     >
            >


Re: Reproducible builds and RPM packages

Jate Sujjavanich
 

I have sussed out several behaviors of the image build having to do with reproducible builds. It seems like bitbake creates the rpm with the correct modification times per the reproducible_builds bbclass. When do_rootfs installs the packages, the timestamps seem correct.

The function reproducible_final_image_task sets all files in rootfs to be REPRODUCIBLE_TIMESTAMP_ROOTFS which is the last commit time in poky by default. This occurs after package installation and before image creation.

When the image creation code runs, it seems like each utility has different behavior on respecting SOURCE_DATE_EPOCH in the environment. The ext3 utility allowed mtime's beyond the default value of 0. The squashfs utility enforced the restriction of no mtime's being beyond 0 seconds since the epoch. Once I set this to the build timestamp (DATETIME) in the image recipe, the squashfs image had correct times.

So to get this working, you'd need to disable reproducible_final_image_task, and make sure the image creation utility is not wiping out the modification times of files created by rpm.

I'd argue that we'd want reproducible_final_image_task to not override all the mtime's of files. We probably have to check the other file system type to see their behavior with SOURCE_DATE_EPOCH as well.

- Jate


Re: Qtwebengine recipe in yocto zeus (latest version) #yocto #zeus #qt

Khem Raj
 

On 11/12/20 8:29 AM, anthony.marchand@navocap.com wrote:
Hello.
I hope you're going well in this period.
I'm working with yocto (zeus version) with a soc i.MX6 and kernel 4.19. Actually, I meet a weird issue about the recipe "qtwebengine" in all of my projects that are using zeus version.
The compilation was working fine until there, but since approximatively two weeks, with no particular reason, whatever the project I want to compile, I'm unable to compile qtwebengine and making a rootfs image with it inside.
So I have tested:
1) bitbake qtwebengine
2) bitbake myimage
PS: myimage contain the recipe qtwebengine.
But whatever the bitbake commands 1 or 2, Bitbake shows me the same error I don't understand and this error follows:
-----------------------------------------------------------------------------------
| In file included from /usr/include/bits/errno.h:26:0,
|                  from /usr/include/errno.h:28,
|                  from /usr/include/c++/7/cerrno:42,
|                  from /usr/include/c++/7/ext/string_conversions.h:44,
|                  from /usr/include/c++/7/bits/basic_string.h:6361,
|                  from /usr/include/c++/7/string:52,
|                  from /usr/include/c++/7/stdexcept:39,
|                  from /usr/include/c++/7/array:39,
|                  from /usr/include/c++/7/tuple:39,
|                  from /usr/include/c++/7/bits/unique_ptr.h:37,
|                  from /usr/include/c++/7/memory:80,
|                  from ../../../../git/src/3rdparty/chromium/v8/src/torque/cfg.h:9,
|                  from ./../../../../git/src/3rdparty/chromium/v8/src/torque/cfg.cc:5,
|                  from v8_snapshot/gen/v8/torque_base_jumbo_1.cc:5:
| /usr/include/linux/errno.h:1:10: fatal error: asm/errno.h: No such file or directory
|  #include <asm/errno.h>
|           ^~~~~~~~~~~~~
| compilation terminated.
...
| Makefile.gn_run:340: recipe for target 'run_ninja' failed
| make[3]: *** [run_ninja] Error 1
| make[3]: Leaving directory '/home/yocto/Dev/build_zeus/tmp/work/cortexa9t2hf-neon-mx6qdl-poky-linux-gnueabi/qtwebengine/5.13.0+gitAUTOINC+5d4bac57a0_8a28c0bb19-r0/build/src/core'
| Makefile:82: recipe for target 'sub-gn_run-pro-make_first' failed
| make[2]: *** [sub-gn_run-pro-make_first] Error 2
| make[2]: Leaving directory '/home/yocto/Dev/build_zeus/tmp/work/cortexa9t2hf-neon-mx6qdl-poky-linux-gnueabi/qtwebengine/5.13.0+gitAUTOINC+5d4bac57a0_8a28c0bb19-r0/build/src/core'
| Makefile:76: recipe for target 'sub-core-make_first' failed
| make[1]: *** [sub-core-make_first] Error 2
| make[1]: Leaving directory '/home/yocto/Dev/build_zeus/tmp/work/cortexa9t2hf-neon-mx6qdl-poky-linux-gnueabi/qtwebengine/5.13.0+gitAUTOINC+5d4bac57a0_8a28c0bb19-r0/build/src'
| Makefile:48: recipe for target 'sub-src-make_first' failed
| make: *** [sub-src-make_first] Error 2
| WARNING: exit code 1 from a shell command.
|
ERROR: Task (/home/yocto/Dev/build_zeus/../meta-qt5/recipes-qt/qt5/qtwebengine_git.bb:do_compile) failed with exit code '1'
-----------------------------------------------------------------------------------
I don't understand why bitbake don't find '<asm/errno.h>', because it is present in the kernel 4.19 and in my host system ubuntu 18. Furthermore, I don't understand the problem with run_ninja.
I try to change my PC for compilation, but I have got the same error. The PC I use to compile with bitbake got 20 cores intel xeon and 32GB of ram. I think the problem is not from here. :-)
Does someone already meet this problem?
Does someone know where could be the problem?
it seems to be failing to find files on build host install and there were similar issues seen on chromium browswer long time ago which has been addressed in meta-browser. you might disable building torque perhaps to workaround it.

Thanks for all and best reguards: Anthony.


Re: Patch files before recipe is parsed

 

On Thu, 12 Nov 2020 at 17:14, Paul Adams <paul.adams@evogro.com> wrote:

There is a problem with the Yocto recipe for Python 3 in warrior. It
is missing ntpath in the list of core modules listed in
python3-manifest.json.

Since warrior is EOL, I was hoping to fix this by patching the
python3-manifest.json file but it doesn't work. I think the reason is
that the manifest file is read by an anonymous function in the recipe,
which I understand is executed during recipe parsing (which I assume
happens before the patches are applied).

I know the patch is being applied correctly because the content of
python3-manifest.json file is correct when I inspect it in the
build/tmp/work... directory.

My question is whether there is any method in bitbake to apply patches
early enough to fix this issue?
There's nothing in bitbake to support this. If you need to carry
patches against an EOL branch then you can either create a local fork
of poky or use a setup tool like kas (https://github.com/siemens/kas)
which can apply patches when checking out layers.

The better alternative would be to upgrade to a supported branch if
you can though.

Thanks,

--
Paul Barker
Konsulko Group


Re: #yocto "zeus" #yocto

Khem Raj
 

are you using nfsvers= in /etc/fstab

On Thu, Nov 12, 2020 at 10:44 AM Monsees, Steven C (US) via
lists.yoctoproject.org
<steven.monsees=baesystems.com@lists.yoctoproject.org> wrote:



All things being equal, would you know why I might see

"NFS: bad mount option value specified: minorversion=1"

when running app under "zeus" but not under "rocko" ?

-----Original Message-----
From: Khem Raj [mailto:raj.khem@gmail.com]
Sent: Thursday, November 12, 2020 1:40 PM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>; yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto "zeus"

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.



On 11/12/20 4:03 AM, Monsees, Steven C (US) via lists.yoctoproject.org
wrote:
This is probably a simple question, but since I am new to yocto there
is a lot to learn...

How do I establish kernel access permissions for the "zeus" kernel so
that when my application is up and running, (or an application startup
script), can create read/write files for access/updating in the "/etc"
and "/dev" directories ?

In the few cases I do this I am seeing unable to open errors...

Note the same code appears to work correctly under "rocko"...
you have to provide more context to help you more, but usually /dev is populated with devtmpfs during kernel boot. and similarly /etc is mounted early on. So access permissions could be mounting issues perhaps.


Thanks,

Steve







Re: #yocto "zeus" #yocto

Monsees, Steven C (US)
 

All things being equal, would you know why I might see

"NFS: bad mount option value specified: minorversion=1"

when running app under "zeus" but not under "rocko" ?

-----Original Message-----
From: Khem Raj [mailto:raj.khem@gmail.com]
Sent: Thursday, November 12, 2020 1:40 PM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>; yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto "zeus"

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.



On 11/12/20 4:03 AM, Monsees, Steven C (US) via lists.yoctoproject.org
wrote:
This is probably a simple question, but since I am new to yocto there
is a lot to learn...

How do I establish kernel access permissions for the "zeus" kernel so
that when my application is up and running, (or an application startup
script), can create read/write files for access/updating in the "/etc"
and "/dev" directories ?

In the few cases I do this I am seeing unable to open errors...

Note the same code appears to work correctly under "rocko"...
you have to provide more context to help you more, but usually /dev is populated with devtmpfs during kernel boot. and similarly /etc is mounted early on. So access permissions could be mounting issues perhaps.


Thanks,

Steve





Re: #yocto "zeus" #yocto

Khem Raj
 

On 11/12/20 4:03 AM, Monsees, Steven C (US) via lists.yoctoproject.org wrote:
This is probably a simple question, but since I am new to yocto there is a lot to learn…
How do I establish kernel access permissions for the “zeus” kernel so that when my application is up and running, (or an application startup script), can create read/write files for access/updating in the ”/etc” and “/dev” directories ?
In the few cases I do this I am seeing unable to open errors…
Note the same code appears to work correctly under “rocko”…
you have to provide more context to help you more, but usually /dev is populated with devtmpfs during kernel boot. and similarly /etc is mounted early on. So access permissions could be mounting issues perhaps.

Thanks,
Steve


Patch files before recipe is parsed

Paul Adams
 

There is a problem with the Yocto recipe for Python 3 in warrior. It
is missing ntpath in the list of core modules listed in
python3-manifest.json.

Since warrior is EOL, I was hoping to fix this by patching the
python3-manifest.json file but it doesn't work. I think the reason is
that the manifest file is read by an anonymous function in the recipe,
which I understand is executed during recipe parsing (which I assume
happens before the patches are applied).

I know the patch is being applied correctly because the content of
python3-manifest.json file is correct when I inspect it in the
build/tmp/work... directory.

My question is whether there is any method in bitbake to apply patches
early enough to fix this issue?


Qtwebengine recipe in yocto zeus (latest version) #yocto #zeus #qt

anthony.marchand@...
 

Hello.
I hope you're going well in this period.
I'm working with yocto (zeus version) with a soc i.MX6 and kernel 4.19. Actually, I meet a weird issue about the recipe "qtwebengine" in all of my projects that are using zeus version.
The compilation was working fine until there, but since approximatively two weeks, with no particular reason, whatever the project I want to compile, I'm unable to compile qtwebengine and making a rootfs image with it inside.

So I have tested:

1) bitbake qtwebengine
2) bitbake myimage

PS: myimage contain the recipe qtwebengine.

But whatever the bitbake commands 1 or 2, Bitbake shows me the same error I don't understand and this error follows:

-----------------------------------------------------------------------------------
| In file included from /usr/include/bits/errno.h:26:0,
|                  from /usr/include/errno.h:28,
|                  from /usr/include/c++/7/cerrno:42,
|                  from /usr/include/c++/7/ext/string_conversions.h:44,
|                  from /usr/include/c++/7/bits/basic_string.h:6361,
|                  from /usr/include/c++/7/string:52,
|                  from /usr/include/c++/7/stdexcept:39,
|                  from /usr/include/c++/7/array:39,
|                  from /usr/include/c++/7/tuple:39,
|                  from /usr/include/c++/7/bits/unique_ptr.h:37,
|                  from /usr/include/c++/7/memory:80,
|                  from ../../../../git/src/3rdparty/chromium/v8/src/torque/cfg.h:9,
|                  from ./../../../../git/src/3rdparty/chromium/v8/src/torque/cfg.cc:5,
|                  from v8_snapshot/gen/v8/torque_base_jumbo_1.cc:5:
| /usr/include/linux/errno.h:1:10: fatal error: asm/errno.h: No such file or directory
|  #include <asm/errno.h>
|           ^~~~~~~~~~~~~
| compilation terminated.
...
| Makefile.gn_run:340: recipe for target 'run_ninja' failed
| make[3]: *** [run_ninja] Error 1
| make[3]: Leaving directory '/home/yocto/Dev/build_zeus/tmp/work/cortexa9t2hf-neon-mx6qdl-poky-linux-gnueabi/qtwebengine/5.13.0+gitAUTOINC+5d4bac57a0_8a28c0bb19-r0/build/src/core'
| Makefile:82: recipe for target 'sub-gn_run-pro-make_first' failed
| make[2]: *** [sub-gn_run-pro-make_first] Error 2
| make[2]: Leaving directory '/home/yocto/Dev/build_zeus/tmp/work/cortexa9t2hf-neon-mx6qdl-poky-linux-gnueabi/qtwebengine/5.13.0+gitAUTOINC+5d4bac57a0_8a28c0bb19-r0/build/src/core'
| Makefile:76: recipe for target 'sub-core-make_first' failed
| make[1]: *** [sub-core-make_first] Error 2
| make[1]: Leaving directory '/home/yocto/Dev/build_zeus/tmp/work/cortexa9t2hf-neon-mx6qdl-poky-linux-gnueabi/qtwebengine/5.13.0+gitAUTOINC+5d4bac57a0_8a28c0bb19-r0/build/src'
| Makefile:48: recipe for target 'sub-src-make_first' failed
| make: *** [sub-src-make_first] Error 2
| WARNING: exit code 1 from a shell command.
|
ERROR: Task (/home/yocto/Dev/build_zeus/../meta-qt5/recipes-qt/qt5/qtwebengine_git.bb:do_compile) failed with exit code '1'
-----------------------------------------------------------------------------------

I don't understand why bitbake don't find '<asm/errno.h>', because it is present in the kernel 4.19 and in my host system ubuntu 18. Furthermore, I don't understand the problem with run_ninja.

I try to change my PC for compilation, but I have got the same error. The PC I use to compile with bitbake got 20 cores intel xeon and 32GB of ram. I think the problem is not from here. :-)

Does someone already meet this problem?

Does someone know where could be the problem?

Thanks for all and best reguards: Anthony.


#yocto "zeus" #yocto

Monsees, Steven C (US)
 

 

This is probably a simple question, but since I am new to yocto there is a lot to learn…

 

How do I establish kernel access permissions for the “zeus” kernel so that when my application is up and running, (or an application startup script), can create read/write files for access/updating in the ”/etc” and “/dev” directories ?

 

In the few cases I do this I am seeing unable to open errors…

Note the same code appears to work correctly under “rocko”…

 

Thanks,

Steve


Re: Emulator tool for imx8m #linux #devtool #yocto

Amrun Nisha.R
 

Thanks Andy,

I tried to boot the linux kernel using TFTP/NFS, i got this below error

BOOTP broadcast 1
DHCP client bound to address 10.78.216.7 (12 ms)
Using ethernet@30be0000 device
TFTP from server 199.63.127.45; our IP address is 10.78.216.7; sending through gateway 10.79.108.1
Filename 'boot\x86\wdsnbp.com'.
Load address: 0x42000000
Loading: *
ARP Retry count exceeded; starting again
Error: Bad gzipped data
fdt_file=fsl-imx8mq-var-dart.dtb
BOOTP broadcast 1
DHCP client bound to address 10.78.216.7 (17 ms)
Using ethernet@30be0000 device
TFTP from server 199.63.127.45; our IP address is 10.78.216.7; sending through gateway 10.79.108.1
Filename 'boot\x86\wdsnbp.com'.
Load address: 0x43000000
Loading: *
ARP Retry count exceeded; starting again
WARN: Cannot load the DT

is there any way to fix this issue?


Issue related to .wic image

NIKHIL PATIL
 

Hi ,
    We are compiling a core-image-sato-sdk.wic  image  using bitbake  that time i am not able to copy anything into /lib/firmware  folder. 
     but when i am compiling core-image-sato-sdk.hddimg   that time its work fine .     
    for wic image getting following error .
  
root@intel-corei7-64:~# cp tests/Firmware/* /lib/firmware/
cp: cannot create regular file '/lib/firmware/RS9113_AP_BT_DUAL_MODE.rps': Read-only file system
cp: cannot create regular file '/lib/firmware/RS9113_WC_BL.rps': Read-only file system


#yocto zeus X11 keyboard #yocto

Monsees, Steven C (US)
 

 

I am running zeus based image (that runs without the following error under  my rocko build), under zeus build I am now seeing the following :

 

The XKEYBOARD keymap compiler (xkbcomp) reports:

> Warning:          Unsupported high keycode 372 for name <I372> ignored

>                   X11 cannot support keycodes above 255.

>                   This warning only shows for the first high keycode.

Errors from xkbcomp are not fatal to the X server

 

Under: .../share/X11/xkb/keycodes/evfev I372 is defined as:

        // Extended keys that may be generated on "Internet" keyboards.

        // evdev has standardize names for these.

 

        <I372> = 372;   // #define KEY_FAVORITES           364

 

Is there a build option for this component I can tweak to correct for this ?

 

Thanks,

Steve


Re: Split kernel patches over different machines

Bel Hadj Salem Talel
 

Hi,
Thanks for the reply,

Yes, that did the trick.

Thanks, Talel


Re: Split kernel patches over different machines

Quentin Schulz
 

Hi Talel,

On Wed, Nov 11, 2020 at 03:30:33AM -0800, Bel Hadj Salem Talel wrote:
Hi All,

I created two different machines "menzu-console" and "menzu-media"
I have main patch for device tree for both , and only one patch specific for menzu-media machine
So in the linux recipe bbappend I want to set something like this:
SRC_URI += "file://main.patch" # FOR BOTH MACHINES
SRC_URI_menzu-media += "file://media.patch" # FOR menzu-media ONLY
SRC_URI_append_mezu-media = " file://media.patch"
is what you should use.

The issue with your suggestion is that it **replaces** the original
variable iff the recipe is built for menzu-media. What you want is to
append to the variable iff the recipe is built for menzu-media, that's
what the line above does.

Quentin


Split kernel patches over different machines

Bel Hadj Salem Talel
 

Hi All,

I created two different machines "menzu-console" and "menzu-media"
I have main patch for device tree for both , and only one patch specific for menzu-media machine
So in the linux recipe bbappend I want to set something like this:
SRC_URI += "file://main.patch" # FOR BOTH MACHINES
SRC_URI_menzu-media += "file://media.patch" # FOR menzu-media ONLY

But this didn't work, only "media.patch" is unpacked and moreover the kernel recipe workdir does not contain a content as if unpack didn't work properly.
How can I do it ?

Thanks, Talel


Re: : When compiling code, how to make a package not hash checked?

ouyangxuan10@163.com
 

hi Quentin,








At 2020-11-10 21:16:15, "Quentin Schulz" <quentin.schulz@...> wrote: >Hi Byron, > >On Tue, Nov 10, 2020 at 09:09:05PM +0800, ouyangxuan10@... wrote: >> Dear all, >> >> >> I would like to ask the reasons for the following problems and how to solve them? When compiling a program, how to make a package not hash checked? >> > >Did you execute the commands that were suggested in the log you sent? > >Can you send us the content of the log of the second command please?
>
This is another package with the same problem:(Run the above command.)

the log in locked-sigs.inc

I would like to ask, is there any way to separate this package from the verification function?

>Basically, two possible ways this happens: > 1. you modified the recipe while bitbake was running. Solution => don't > do that. > 2. bitbake parses tasks multiple times during a run, therefore, if a > variable changes between parses your task will have a different hash. > This usually happens with DATETIME. If you don't absolutely need this > variable, remove it or find a replacement. If you have to, I think the > vardepsexclude variable flag is the way to do it? >
>Quentin

Thanks,
Byron


 


Re: python bump

Mikko Rapeli
 

On Wed, Nov 11, 2020 at 08:39:42AM +0100, Belisko Marek wrote:
On Wed, Nov 11, 2020 at 8:04 AM <Mikko.Rapeli@bmw.de> wrote:

Hi,

On Tue, Nov 10, 2020 at 07:44:39PM +0100, Marek Belisko wrote:
Hi,

I'm using poky release thud and would like to bump python3 to 3.8.x. I
took recipe from most recent poky version but I'm hitting issue with
e.g. meson build like:
Log data follows:
| DEBUG: Executing shell function do_configure
| Traceback (most recent call last):
| File "setup.py", line 25, in <module>
| from setuptools import setup
| ModuleNotFoundError: No module named 'setuptools'

Are there some other things I need to take care when want to bump python3?
When backporting changes, I find it better to cherry-pick the changes for e.g.
python3 update from master to the old branch that I have to use. In my case I can
not update anything which breaks ABIs on target images but can update all
development tools like python3. Often fixes and/or updates to components which
fail to build are also easy to find from master and cherry-pick, especially if you
don't need to build all recipes from poky but only a certain subset. Over
time this will make your local branch look horrible though, but at least
merges from stable branches will in most cases work, if they are still alive.
Thanks for sharing. But I'm using official poky release from git so I
cannot cherry pick changes.
Or you have clone of poky repo and add changes on top from newest versions?
Locally, as developer you always have a local branch where you can cherry-pick
changes. With git submodules and repo tooling, you should use a local or
project specific clone of poky. Or move all updates and changes to your own
layers, but I find this doesn't scale and instead branching in git works
better.

Cheers,

-Mikko

4061 - 4080 of 55412