|
[meta-virtualization]: dunfell docker run issues
Marek, This might indeed indicate a configuration mismatch. Lots of stuff comes up on Google that you might want to check. One is a change in systemd that affects this. Sorry I don't have a link ready
Marek, This might indeed indicate a configuration mismatch. Lots of stuff comes up on Google that you might want to check. One is a change in systemd that affects this. Sorry I don't have a link ready
|
By
Leon Woestenberg
· #52252
·
|
|
Appropriate patch posting location?
Hi Kent, Most of these providers provide an IMAP interface as well, such as gmail. Also, in gmail you can tag messages to move into a separate folder for easy delete. For devs and users, the patches a
Hi Kent, Most of these providers provide an IMAP interface as well, such as gmail. Also, in gmail you can tag messages to move into a separate folder for easy delete. For devs and users, the patches a
|
By
Leon Woestenberg
· #52247
·
|
|
#yocto CORE_IMAGE_EXTRA_INSTALL Where can I find a list of valid package names?
#yocto
Hello, What's obvious? There are no package names there, only recipe names that I am aware of. So for the non-obvious packages it still is a bit of guesswork, or the responses in this thread. Regards,
Hello, What's obvious? There are no package names there, only recipe names that I am aware of. So for the non-obvious packages it still is a bit of guesswork, or the responses in this thread. Regards,
|
By
Leon Woestenberg
· #52246
·
|
|
Building eSDK fails
#sdk
Hello Alexander, I have two ideas that might get you closer. 1) First, I noticed that using TOOLCHAIN_HOST_TASK += "xxx" is broken on Yocto dunfell for me (non-extensible SDK). The issue is that even
Hello Alexander, I have two ideas that might get you closer. 1) First, I noticed that using TOOLCHAIN_HOST_TASK += "xxx" is broken on Yocto dunfell for me (non-extensible SDK). The issue is that even
|
By
Leon Woestenberg
· #52240
·
|
|
Can't Build Read-Only RootFS
Hello Dave, I copied that error report into Google. Maybe you are hitting a similar case to this? https://www.yoctoproject.org/pipermail/meta-xilinx/2018-January/003638.html Regards, Leon,
Hello Dave, I copied that error report into Google. Maybe you are hitting a similar case to this? https://www.yoctoproject.org/pipermail/meta-xilinx/2018-January/003638.html Regards, Leon,
|
By
Leon Woestenberg
· #52017
·
|
|
cpio issues
Hello Damien, I have this in my local.conf: IMAGE_FSTYPES = "tar ext4" INITRAMFS_FSTYPES = "cpio.xz" It does depend a bit on your image recipes and classes if this works for you. Regards, Leon.
Hello Damien, I have this in my local.conf: IMAGE_FSTYPES = "tar ext4" INITRAMFS_FSTYPES = "cpio.xz" It does depend a bit on your image recipes and classes if this works for you. Regards, Leon.
|
By
Leon Woestenberg
· #52014
·
|
|
#yocto #sdk How to add *-dev packages to sdk installer and not to target rootfs
#yocto
#sdk
Hello Henrik, As far as I known: - The -dev packages do not end up in target rootfs, unless you specify them in your target image. - The -dev packages end up in the standard SDK target sysroot if you
Hello Henrik, As far as I known: - The -dev packages do not end up in target rootfs, unless you specify them in your target image. - The -dev packages end up in the standard SDK target sysroot if you
|
By
Leon Woestenberg
· #50925
·
|
|
SIGINT Issues with Zeus Migration
Hello Aashik, I recognize the issue that CTRL-C does not pass from the console, but only with *very* minimal configurations. How does your local.conf look like, or better yet how can we reproduce your
Hello Aashik, I recognize the issue that CTRL-C does not pass from the console, but only with *very* minimal configurations. How does your local.conf look like, or better yet how can we reproduce your
|
By
Leon Woestenberg
· #50825
·
|
|
SIGINT Issues with Zeus Migration
Hi Aashik, Zoran, Aashik, how are you sending the signal? Using CTRL-C or using the "kill" command? That reads to use sigaction() instead of signal() I would assume. Zoran, are you suggesting that pro
Hi Aashik, Zoran, Aashik, how are you sending the signal? Using CTRL-C or using the "kill" command? That reads to use sigaction() instead of signal() I would assume. Zoran, are you suggesting that pro
|
By
Leon Woestenberg
· #50814
·
|
|
#sdk #yocto Appears SDK searching host for files that are only present on target side
#sdk
#yocto
Hello Steven, you mention you use CMake with the Yocto (standard) SDK. After you sourced the SDK environment script, what is the output of "which cmake" ? Do you use the cmake toolchain configuration
Hello Steven, you mention you use CMake with the Yocto (standard) SDK. After you sourced the SDK environment script, what is the output of "which cmake" ? Do you use the cmake toolchain configuration
|
By
Leon Woestenberg
· #50638
·
|
|
meta-intel: Override SERIAL_CONSOLES variable
Hi all, For a more generic solution, could this be made a weak assignment? I am on a SMARC x86-64 module which only one serial is useful, so I would like to downtune this variable as well. Regards, Le
Hi all, For a more generic solution, could this be made a weak assignment? I am on a SMARC x86-64 module which only one serial is useful, so I would like to downtune this variable as well. Regards, Le
|
By
Leon Woestenberg
· #49113
·
|
|
dev-manual: differing versions of same recipe in different priority layers?
Hello Robert, <rpjday@...> wrote: Yes, this should be re-worded. This is actually a FAQ. (I remember more sentences like this exist, that especially for non-English speakers might be diffic
Hello Robert, <rpjday@...> wrote: Yes, this should be re-worded. This is actually a FAQ. (I remember more sentences like this exist, that especially for non-English speakers might be diffic
|
By
Leon Woestenberg
· #48393
·
|
|
clarifying "PROVIDES =" versus "PROVIDES +=" (pedantic stuff)
Hello Robert, My understanding is that: means "I provide both "libpcre" as well as "pcre". I am assuming that PROVIDES = "${PN}" is already set by a core BitBake rule somewhere. (Didn't check...) So I
Hello Robert, My understanding is that: means "I provide both "libpcre" as well as "pcre". I am assuming that PROVIDES = "${PN}" is already set by a core BitBake rule somewhere. (Didn't check...) So I
|
By
Leon Woestenberg
· #48307
·
|
|
Architecture of .wic approach; image of images
My finding is: ...only if *artifacts* (also) includes a rootfs. The image class dependency on rootfs seems very hardcoded. I cannot create a recipe that works without *creating* a rootfs. (even though
My finding is: ...only if *artifacts* (also) includes a rootfs. The image class dependency on rootfs seems very hardcoded. I cannot create a recipe that works without *creating* a rootfs. (even though
|
By
Leon Woestenberg
· #47461
·
|
|
Architecture of .wic approach; image of images
<holzmayr@...> wrote: Yes, up to there everything is clean and nice. And I understand I can build multiple images. I have used this feature since 2006. My point is, that we do not su
<holzmayr@...> wrote: Yes, up to there everything is clean and nice. And I understand I can build multiple images. I have used this feature since 2006. My point is, that we do not su
|
By
Leon Woestenberg
· #47459
·
|
|
Architecture of .wic approach; image of images
So let's then consider the case that the WKS is machine specific. I am fine with that. - Does Yocto support building multiple images from one configuration? - (How) can I build multiple WIC images wit
So let's then consider the case that the WKS is machine specific. I am fine with that. - Does Yocto support building multiple images from one configuration? - (How) can I build multiple WIC images wit
|
By
Leon Woestenberg
· #47457
·
|
|
Architecture of .wic approach; image of images
<holzmayr@...> wrote: IMAGE_FSTYPES += "wic" goes in the image recipe, yes. WKS_FILE is there as well for this image, because I need to create multiple images with different WKS's. I
<holzmayr@...> wrote: IMAGE_FSTYPES += "wic" goes in the image recipe, yes. WKS_FILE is there as well for this image, because I need to create multiple images with different WKS's. I
|
By
Leon Woestenberg
· #47454
·
|
|
Architecture of .wic approach; image of images
Let me then first describe the issue I am having, which I think results from my misunderstanding then. I would like to package a UEFI bootloader (GRUB), bzImage and initramfs.cpio.gz into an FAT parti
Let me then first describe the issue I am having, which I think results from my misunderstanding then. I would like to package a UEFI bootloader (GRUB), bzImage and initramfs.cpio.gz into an FAT parti
|
By
Leon Woestenberg
· #47451
·
|
|
Architecture of .wic approach; image of images
Hello all, What is the intended approach of building images using WIC? Most image types (except .wic) build a (root or initial ram) filesystem from *packages*, then create the respective archive or fi
Hello all, What is the intended approach of building images using WIC? Most image types (except .wic) build a (root or initial ram) filesystem from *packages*, then create the respective archive or fi
|
By
Leon Woestenberg
· #47445
·
|
|
Memory Tests in U-Boot
Hello, We found stressapptest (by Google) the most reliable test for DDR calibration problems. We have seen unreliable systems pass other memory tests such as in U-Boot. Regards, Leon
Hello, We found stressapptest (by Google) the most reliable test for DDR calibration problems. We have seen unreliable systems pass other memory tests such as in U-Boot. Regards, Leon
|
By
Leon Woestenberg
· #47393
·
|