Date   

Re: Enaable to add binary in /usr/bin using .bb file

NIKHIL PATIL <nikhilvp29@...>
 

Hi ,
    If anyone know , please help on these .

On Thu, Nov 19, 2020 at 1:14 PM NIKHIL PATIL via lists.yoctoproject.org <nikhilvp29=gmail.com@...> wrote:
Hi ,
    I want to add binary in /usr/bin , for these i made own .bb file (obexpushtest.bb),      When i am compiling obexpushtest package separately that time it is compiling fine  , but when i am adding obexpushtest in local.conf as a IMAGE_INSTALL , i am getting error.

## Error :-

/data/nikhil/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-intel/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:01 ago on Thu 19 Nov 2020 05:57:19 AM UTC.
No match for argument: obexpushtest
Error: Unable to find a match
    
## obexpushtest.bb file :-

    # file recipes-kernel/linux-firmware/linux-firmware_%.bbappend
SUMMARY = "tset_mount example"
SECTION = "test_mount"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

S = "${WORKDIR}"

SRC_URI += "file://obexpushd"

INSANE_SKIP_${PN} = "ldflags"
INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
INHIBIT_PACKAGE_STRIP = "1"

do_install_append () {
        install -d ${D}/${bindir}
        install -m 0644 ${WORKDIR}/obexpushd ${D}/${bindir}
        cp ${WORKDIR}/obexpushd ${D}/${bindir}
}

# NOTE: Use "=+" instead of "+=". Otherwise, the file is placed into the linux-firmware package.
PACKAGES =+ "${PN}-example"
FILES_${PN}-example = "/usr/bin/obexpushd"









Enaable to add binary in /usr/bin using .bb file

NIKHIL PATIL <nikhilvp29@...>
 

Hi ,
    I want to add binary in /usr/bin , for these i made own .bb file (obexpushtest.bb),      When i am compiling obexpushtest package separately that time it is compiling fine  , but when i am adding obexpushtest in local.conf as a IMAGE_INSTALL , i am getting error.

## Error :-

/data/nikhil/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-intel/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:01 ago on Thu 19 Nov 2020 05:57:19 AM UTC.
No match for argument: obexpushtest
Error: Unable to find a match
    
## obexpushtest.bb file :-

    # file recipes-kernel/linux-firmware/linux-firmware_%.bbappend
SUMMARY = "tset_mount example"
SECTION = "test_mount"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

S = "${WORKDIR}"

SRC_URI += "file://obexpushd"

INSANE_SKIP_${PN} = "ldflags"
INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
INHIBIT_PACKAGE_STRIP = "1"

do_install_append () {
        install -d ${D}/${bindir}
        install -m 0644 ${WORKDIR}/obexpushd ${D}/${bindir}
        cp ${WORKDIR}/obexpushd ${D}/${bindir}
}

# NOTE: Use "=+" instead of "+=". Otherwise, the file is placed into the linux-firmware package.
PACKAGES =+ "${PN}-example"
FILES_${PN}-example = "/usr/bin/obexpushd"






Re: Raspberry PI enabling MMC1

chuck kamas
 

Making some progress here!


I added a compiled version of the attached device tree and now the mmc1 shows up in my yocto image! Yes! Now I need to find out the secret magic in that tree that I need to add...


Chuck


On 11/18/20 7:59 PM, chuck kamas via lists.yoctoproject.org wrote:

Raj,


I found out how to debug the boot process of the PI from:

https://github.com/raspberrypi/documentation/blob/master/hardware/raspberrypi/bootmodes/README.md

by turning on the boot code debug.

sed -i -e "s/BOOT_UART=0/BOOT_UART=1/" bootcode.bin


I found out that the sdio overlay does not exist!

MESS:00:00:07.868162:0: dtdebug: Failed to open overlay file 'overlays/sdio.dtbo'
MESS:00:00:07.874093:0: Failed to load overlay 'sdio'
MESS:00:00:07.878881:0: brfs: File read: /mfs/sd/overlays/sdio.dtbo
MESS:00:00:07.891322:0: brfs: File read: /mfs/sd/cmdline.txt


So what am I missing on how to turn on the sdio on GPIO22-27? Is it not an overlay and instead a driver/other code/linux config that needs to be set?


Chuck


On 11/17/20 4:29 PM, chuck kamas via lists.yoctoproject.org wrote:
Raj,


Thanks for taking the time to respond. I thought of that too. My custom Yocto build has the line to turn on the sdio in it:

dtoverlay=sdio,poll_once=off

I have attached the entire file: config.txt.yocto

However, the Rasbian image does not have any mention of the dtoverlay for the sdio.  Curious. See config.txt attached.


Thanks for the help!

Chuck


On 11/17/20 12:08 AM, Khem Raj wrote:
On Mon, Nov 16, 2020 at 11:43 PM chuck kamas via
lists.yoctoproject.org <chuckkamas=yahoo.com@...>
wrote:
Hi all,


I have been spinning my wheels for two days trying to discover how to
enable MMC1 on a CM3. This is the one on GPIO22-27. I can boot Rasbian
on the CM3 and it inits the MMC1 and its pins just fine. I can
read/write to my SD card from it etc. However, when I build yocto it
leaves the GPIOS22-27 in gpio mode and does not set them to MMC1 mode.
I have tried changing the device tree as described here:

https://stackoverflow.com/questions/44702426/how-to-setup-an-own-device-tree-for-a-raspberrypi-in-yocto

That compiles and add the .dtbo to my build, but still the GPIOS are not
set to MMC1 mode.

cat /sys/kernel/debug/pinctrl/*gpio*/pinmux-pins
Pinmux settings per pin
Format: pin (name): mux_owner gpio_owner hog?
....

pin 22 (gpio22): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 23 (gpio23): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 24 (gpio24): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 25 (gpio25): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 26 (gpio26): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 27 (gpio27): (MUX UNCLAIMED) (GPIO UNCLAIMED)

.....

I have looked at:

https://ralimtek.com/raspberry%20pi/electronics/software/raspberry_pi_secondary_sd_card/


Any ideas of where to look next to turn on the sdio would be appreciated!


what does /boot/config.txt look like on raspbian and yocto built images

Chuck










      




Re: Raspberry PI enabling MMC1

chuck kamas
 

Raj,


I found out how to debug the boot process of the PI from:

https://github.com/raspberrypi/documentation/blob/master/hardware/raspberrypi/bootmodes/README.md

by turning on the boot code debug.

sed -i -e "s/BOOT_UART=0/BOOT_UART=1/" bootcode.bin


I found out that the sdio overlay does not exist!

MESS:00:00:07.868162:0: dtdebug: Failed to open overlay file 'overlays/sdio.dtbo'
MESS:00:00:07.874093:0: Failed to load overlay 'sdio'
MESS:00:00:07.878881:0: brfs: File read: /mfs/sd/overlays/sdio.dtbo
MESS:00:00:07.891322:0: brfs: File read: /mfs/sd/cmdline.txt


So what am I missing on how to turn on the sdio on GPIO22-27? Is it not an overlay and instead a driver/other code/linux config that needs to be set?


Chuck


On 11/17/20 4:29 PM, chuck kamas via lists.yoctoproject.org wrote:
Raj,


Thanks for taking the time to respond. I thought of that too. My custom Yocto build has the line to turn on the sdio in it:

dtoverlay=sdio,poll_once=off

I have attached the entire file: config.txt.yocto

However, the Rasbian image does not have any mention of the dtoverlay for the sdio.  Curious. See config.txt attached.


Thanks for the help!

Chuck


On 11/17/20 12:08 AM, Khem Raj wrote:
On Mon, Nov 16, 2020 at 11:43 PM chuck kamas via
lists.yoctoproject.org <chuckkamas=yahoo.com@...>
wrote:
Hi all,


I have been spinning my wheels for two days trying to discover how to
enable MMC1 on a CM3. This is the one on GPIO22-27. I can boot Rasbian
on the CM3 and it inits the MMC1 and its pins just fine. I can
read/write to my SD card from it etc. However, when I build yocto it
leaves the GPIOS22-27 in gpio mode and does not set them to MMC1 mode.
I have tried changing the device tree as described here:

https://stackoverflow.com/questions/44702426/how-to-setup-an-own-device-tree-for-a-raspberrypi-in-yocto

That compiles and add the .dtbo to my build, but still the GPIOS are not
set to MMC1 mode.

cat /sys/kernel/debug/pinctrl/*gpio*/pinmux-pins
Pinmux settings per pin
Format: pin (name): mux_owner gpio_owner hog?
....

pin 22 (gpio22): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 23 (gpio23): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 24 (gpio24): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 25 (gpio25): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 26 (gpio26): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 27 (gpio27): (MUX UNCLAIMED) (GPIO UNCLAIMED)

.....

I have looked at:

https://ralimtek.com/raspberry%20pi/electronics/software/raspberry_pi_secondary_sd_card/


Any ideas of where to look next to turn on the sdio would be appreciated!


what does /boot/config.txt look like on raspbian and yocto built images

Chuck












Re: [yocto-autobuilder2 PATCH] config.json: drop redundant meta-kernel mentions

Anuj Mittal
 

Hi Ross

On Mon, 2020-11-16 at 14:59 +0000, Ross Burton wrote:
From: Ross Burton <ross.burton@...>
For gatesgarth, this is causing:

FileNotFoundError: [Errno 2] No such file or directory:
'/home/pokybuild/yocto-worker/meta-arm/build/repos/meta-kernel'

https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/472

meta-arm gatesgarth needs meta-kernel?

Thanks,

Anuj

Signed-off-by: Ross Burton <ross.burton@...>
---
 config.json | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/config.json b/config.json
index 11a2664..c57260a 100644
--- a/config.json
+++ b/config.json
@@ -275,9 +275,8 @@
             "TEMPLATE" : "ltp-qemu"
         },
         "meta-arm" : {
-            "NEEDREPOS" : ["poky", "meta-arm", "meta-kernel"],
+            "NEEDREPOS" : ["poky", "meta-arm"],
             "ADDLAYER" : [
-                "${BUILDDIR}/../meta-kernel",
                 "${BUILDDIR}/../meta-arm/meta-arm-toolchain",
                 "${BUILDDIR}/../meta-arm/meta-arm",
                 "${BUILDDIR}/../meta-arm/meta-arm-bsp"



Re: #yocto #yocto

Randy MacLeod
 

On 2020-11-18 8:08 a.m., Monsees, Steven C (US) via lists.yoctoproject.org wrote:
I was going through the kernel boot output and saw the following output, can someone tell me why this might be popping up and how I might modify configuration to resolve? :
.
.
LIMWS (BAE LIMWS base distro) 3.0.4 sbcb-default ttyS0
-sh: cannot set terminal process group (1137): Inappropriate ioctl for device
-sh: no job control in this shell
Hi Steve,

Can you describe your build host and environment and what steps you
take to encounter this error? Does it happen with poky/gatesgarth?

What happens if you follow the steps for:

http://docs.yoctoproject.org/brief-yoctoprojectqs/brief-yoctoprojectqs.html

../Randy
.
.
Thanks,
Steve

--
# Randy MacLeod
# Wind River Linux


Re: qtwayland compile issue 5.15 #dunfell

Khem Raj
 

On 11/17/20 9:40 PM, Khem Raj via lists.yoctoproject.org wrote:
Find QSizeF
newSize(qMax(width, 1.0), qMax(height, 1.0));
in src/compositor/extensions/qwaylandxdgshellv5.cpp
and change it to
newSize(qMax((double)width, 1.0), qMax((double)height, 1.0));
and see if it helps.
btw. qtwaywand worked fine with gcc and clang on latest master for rv64
so please describe any local changes you are carrying

On Tue, Nov 17, 2020 at 6:59 PM sateesh m <sateesh0457@...> wrote:

Hi Guys,

I am getting qtwayland building issue using dunfell version. can anybody help me to solve this issue.



Regards,
Sateesh


loading huawei_cdc_ncm #kernel

Zoltan Kerenyi Nagy
 

Hi,

I'd li to include as a kernel module the huawei_cdc_ncm.c file and autoloaded as a kernel object.

I did this in the main recipie file, but it's not enogh:

KERNEL_MODULE_AUTOLOAD += "cdc_ncm.ko"

I guess I should have a bb file for the huawei_cdc_ncm.c, but I didnt find any on the net.
Could you please help me?

Thanks

Zolee


#yocto #yocto

Monsees, Steven C (US)
 

 

I was going through the kernel boot output and saw the following output, can someone tell me why this might be popping up and how I might modify configuration to resolve? :

.

.

LIMWS (BAE LIMWS base distro) 3.0.4 sbcb-default ttyS0

 

-sh: cannot set terminal process group (1137): Inappropriate ioctl for device

-sh: no job control in this shell

.

.

 

Thanks,

Steve


qtwayland compile issue 5.15 #dunfell

sateesh m
 

Hi Guys,

              I am getting qtwayland building issue using dunfell version. can  anybody help me to solve this issue.



Regards,
Sateesh


Re: [PATCH yocto-autobuilder-helper] auh-config: add non-default distro features

Alexander Kanavin
 

ping :)

Alex


On Tue, 10 Nov 2020 at 09:56, Alexander Kanavin via lists.yoctoproject.org <alex.kanavin=gmail.com@...> wrote:
This adds systemd and pam related recipes to upstream checks and devtool-driven updates.

Signed-off-by: Alexander Kanavin <alex.kanavin@...>
---
 scripts/auh-config/local.conf.append | 1 +
 1 file changed, 1 insertion(+)

diff --git a/scripts/auh-config/local.conf.append b/scripts/auh-config/local.conf.append
index 9628737..b18590f 100644
--- a/scripts/auh-config/local.conf.append
+++ b/scripts/auh-config/local.conf.append
@@ -1,3 +1,4 @@

 INHERIT += "buildhistory"
 LICENSE_FLAGS_WHITELIST = "commercial"
+DISTRO_FEATURES_append = ' systemd pam'
--
2.29.1





Re: Raspberry PI enabling MMC1

chuck kamas
 

Raj,


Thanks for taking the time to respond. I thought of that too. My custom Yocto build has the line to turn on the sdio in it:

dtoverlay=sdio,poll_once=off
I have attached the entire file: config.txt.yocto

However, the Rasbian image does not have any mention of the dtoverlay for the sdio.  Curious. See config.txt attached.


Thanks for the help!

Chuck


On 11/17/20 12:08 AM, Khem Raj wrote:
On Mon, Nov 16, 2020 at 11:43 PM chuck kamas via
lists.yoctoproject.org <chuckkamas=yahoo.com@...>
wrote:
Hi all,


I have been spinning my wheels for two days trying to discover how to
enable MMC1 on a CM3. This is the one on GPIO22-27. I can boot Rasbian
on the CM3 and it inits the MMC1 and its pins just fine. I can
read/write to my SD card from it etc. However, when I build yocto it
leaves the GPIOS22-27 in gpio mode and does not set them to MMC1 mode.
I have tried changing the device tree as described here:

https://stackoverflow.com/questions/44702426/how-to-setup-an-own-device-tree-for-a-raspberrypi-in-yocto

That compiles and add the .dtbo to my build, but still the GPIOS are not
set to MMC1 mode.

cat /sys/kernel/debug/pinctrl/*gpio*/pinmux-pins
Pinmux settings per pin
Format: pin (name): mux_owner gpio_owner hog?
....

pin 22 (gpio22): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 23 (gpio23): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 24 (gpio24): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 25 (gpio25): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 26 (gpio26): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 27 (gpio27): (MUX UNCLAIMED) (GPIO UNCLAIMED)

.....
I have looked at:

https://ralimtek.com/raspberry%20pi/electronics/software/raspberry_pi_secondary_sd_card/


Any ideas of where to look next to turn on the sdio would be appreciated!

what does /boot/config.txt look like on raspbian and yocto built images

Chuck




Re: qtwayland compile issue 5.15 #dunfell

Khem Raj
 

Find QSizeF

newSize(qMax(width, 1.0), qMax(height, 1.0));

in src/compositor/extensions/qwaylandxdgshellv5.cpp

and change it to
newSize(qMax((double)width, 1.0), qMax((double)height, 1.0));

and see if it helps.

On Tue, Nov 17, 2020 at 6:59 PM sateesh m <sateesh0457@...> wrote:

Hi Guys,

I am getting qtwayland building issue using dunfell version. can anybody help me to solve this issue.



Regards,
Sateesh


Re: How to disable specific default recipe to be included in Yocto? #linux #yocto #cups #hplip

Shamil Khan
 

Hi,

You can use BBMASK variable in your configuration file to prevent bitbake from parsing certain recipes.

For example,
BBMASK = "example.bb"
Here, BitBake ignores the example.bb recipe.

Hope this helps!


Re: qtwayland compile issue 5.15 #dunfell

Khem Raj
 

Find QSizeF

newSize(qMax(width, 1.0), qMax(height, 1.0));

in src/compositor/extensions/qwaylandxdgshellv5.cpp

and change it to
newSize(qMax((double)width, 1.0), qMax((double)height, 1.0));

and see if it helps.

On Tue, Nov 17, 2020 at 6:59 PM sateesh m <sateesh0457@...> wrote:

Hi Guys,

I am getting qtwayland building issue using dunfell version. can anybody help me to solve this issue.



Regards,
Sateesh


qtwayland compile issue 5.15 #dunfell

sateesh m
 

Hi Guys,

              I am getting qtwayland building issue using dunfell version. can  anybody help me to solve this issue.



Regards,
Sateesh


Re: Raspberry PI enabling MMC1

chuck kamas
 

Raj,


Thanks for taking the time to respond. I thought of that too. My custom Yocto build has the line to turn on the sdio in it:

dtoverlay=sdio,poll_once=off
I have attached the entire file: config.txt.yocto

However, the Rasbian image does not have any mention of the dtoverlay for the sdio.  Curious. See config.txt attached.


Thanks for the help!

Chuck


On 11/17/20 12:08 AM, Khem Raj wrote:
On Mon, Nov 16, 2020 at 11:43 PM chuck kamas via
lists.yoctoproject.org <chuckkamas=yahoo.com@...>
wrote:
Hi all,


I have been spinning my wheels for two days trying to discover how to
enable MMC1 on a CM3. This is the one on GPIO22-27. I can boot Rasbian
on the CM3 and it inits the MMC1 and its pins just fine. I can
read/write to my SD card from it etc. However, when I build yocto it
leaves the GPIOS22-27 in gpio mode and does not set them to MMC1 mode.
I have tried changing the device tree as described here:

https://stackoverflow.com/questions/44702426/how-to-setup-an-own-device-tree-for-a-raspberrypi-in-yocto

That compiles and add the .dtbo to my build, but still the GPIOS are not
set to MMC1 mode.

cat /sys/kernel/debug/pinctrl/*gpio*/pinmux-pins
Pinmux settings per pin
Format: pin (name): mux_owner gpio_owner hog?
....

pin 22 (gpio22): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 23 (gpio23): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 24 (gpio24): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 25 (gpio25): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 26 (gpio26): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 27 (gpio27): (MUX UNCLAIMED) (GPIO UNCLAIMED)

.....
I have looked at:

https://ralimtek.com/raspberry%20pi/electronics/software/raspberry_pi_secondary_sd_card/


Any ideas of where to look next to turn on the sdio would be appreciated!

what does /boot/config.txt look like on raspbian and yocto built images

Chuck




Re: [PATCH yocto-autobuilder-helper] auh-config: add non-default distro features

Alexander Kanavin
 

ping :)

Alex


On Tue, 10 Nov 2020 at 09:56, Alexander Kanavin via lists.yoctoproject.org <alex.kanavin=gmail.com@...> wrote:
This adds systemd and pam related recipes to upstream checks and devtool-driven updates.

Signed-off-by: Alexander Kanavin <alex.kanavin@...>
---
 scripts/auh-config/local.conf.append | 1 +
 1 file changed, 1 insertion(+)

diff --git a/scripts/auh-config/local.conf.append b/scripts/auh-config/local.conf.append
index 9628737..b18590f 100644
--- a/scripts/auh-config/local.conf.append
+++ b/scripts/auh-config/local.conf.append
@@ -1,3 +1,4 @@

 INHERIT += "buildhistory"
 LICENSE_FLAGS_WHITELIST = "commercial"
+DISTRO_FEATURES_append = ' systemd pam'
--
2.29.1





Re: KeyError: 'getpwuid(): uid not found: 1000' in do_package phase

Marek Belisko
 

On Tue, Nov 17, 2020 at 2:19 PM Nicolas Jeker <n.jeker@...> wrote:

On Mon, 2020-11-16 at 23:27 +0100, Martin Jansa wrote:
https://github.com/webOS-ports/meta-webos-ports/commit/9fd17a67cdbed92df13a14b002a189b4c6c2d442

is an example where it triggers this error, but doesn't trigger the
more common host-user-contaminated QA error (unless you happened to
use UID 1001 on host for the user running bitbake).

Similarly when the files are "installed" with e.g. "cp -a" for which
layers usually use "cp -R --no-dereference --preserve=mode,links -v".
On a related note, the do_install reference in the manual gives some
advice on how to use cp and tar without contaminating the build.

The relevant part:
Thanks all for valuable inputs. Issue solved +1

Safe methods for installing files include the following:
* The install utility. This utility is the preferred method.
* The cp command with the "--no-preserve=ownership" option.
* The tar command with the "--no-same-owner" option. See the
bin_package.bbclass file in the meta/classes directory of the
Source Directory for an example.

https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#ref-tasks-install

On Mon, Nov 16, 2020 at 10:10 PM Marek Belisko <
marek.belisko@...> wrote:
On Mon, Nov 16, 2020 at 9:52 PM Joshua Watt <jpewhacker@...>
wrote:


On 11/16/20 2:38 PM, Marek Belisko wrote:

Hi,

I'm bumping my project based on zeus to dunfell. I've update all
layers and in one of my recipes I'm seeing following issue (not
see on
zeus at all):
WARNING: cv-my-test-1.0-r0 do_package: KeyError in
./package/srv/10%.png
ERROR: cv-my-test-1.0-r0 do_package: Error executing a python
function
in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this
exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function:
<module>
0001:
*** 0002:sstate_report_unihash(d)
0003:
File: '/home/ubuntu/projects/my-test-
/poky/meta/classes/sstate.bbclass',
lineno: 840, function: sstate_report_unihash
0836: report_unihash = getattr(bb.parse.siggen,
'report_unihash', None)
0837:
0838: if report_unihash:
0839: ss = sstate_state_fromvars(d)
*** 0840: report_unihash(os.getcwd(), ss['task'], d)
0841:}
0842:
0843:#
0844:# Shell function to decompress and prepare a package
for installation
File: '/home/ubuntu/projects/my-test-
/poky/bitbake/lib/bb/siggen.py',
lineno: 555, function: report_unihash
0551:
0552: if "." in self.method:
0553: (module, method) =
self.method.rsplit('.', 1)
0554: locs['method'] =
getattr(importlib.import_module(module), method)
*** 0555: outhash =
bb.utils.better_eval('method(path,
sigfile, task, d)', locs)
0556: else:
0557: outhash =
bb.utils.better_eval(self.method +
'(path, sigfile, task, d)', locs)
0558:
0559: try:
File: '/home/ubuntu/projects/my-test-
/poky/bitbake/lib/bb/utils.py',
lineno: 420, function: better_eval
0416: if extraglobals:
0417: ctx = copy.copy(ctx)
0418: for g in extraglobals:
0419: ctx[g] = extraglobals[g]
*** 0420: return eval(source, ctx, locals)
0421:
0422:@contextmanager
0423:def fileslocked(files):
0424: """Context manager for locking and unlocking file
locks."""
File: '<string>', lineno: 1, function: <module>
File "<string>", line 1, in <module>

File: '/home/ubuntu/projects/my-test-
/poky/meta/lib/oe/sstatesig.py',
lineno: 595, function: OEOuthashBasic
0591: process(root)
0592: for f in files:
0593: if f == 'fixmepath':
0594: continue
*** 0595: process(os.path.join(root, f))
0596: finally:
0597: os.chdir(prev_dir)
0598:
0599: return h.hexdigest()
File: '/home/ubuntu/projects/my-test-
/poky/meta/lib/oe/sstatesig.py',
lineno: 551, function: process
0547: add_perm(stat.S_IXOTH, 'x')
0548:
0549: if include_owners:
0550: try:
*** 0551: update_hash(" %10s" %
pwd.getpwuid(s.st_uid).pw_name)
0552: update_hash(" %10s" %
grp.getgrgid(s.st_gid).gr_name)
0553: except KeyError:
0554: bb.warn("KeyError in %s" %
path)
0555: raise
Exception: KeyError: 'getpwuid(): uid not found: 1000'

ERROR: Logfile of failure stored in:
/home/ubuntu/projects/my-test-/build/tmp/work/aarch64-poky-
linux/cv-my-test/1.0-r0/temp/log.do_package.27454

Is this known issue or something related to my host setup?

This means the recipe is having host contamination (where the UID
of the user doing the build is leaking into the file system).
Some ideas what can be the source of that. This recipe is basically
just copying files from archive to final rootfs without any special
processing or so.

Thanks and BR,

marek



BR,

marek






Re: #yocto zeus X11 keyboard #yocto

Monsees, Steven C (US)
 


Is there a way around this ?

5981 - 6000 of 57384