Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dev1990 has quit [Quit: Konversation terminated!]
dev1990 has joined #yocto
Tokamak has joined #yocto
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
prabhakarlad has quit [Ping timeout: 256 seconds]
dev1990 has quit [Quit: Konversation terminated!]
sakoman has quit [Quit: Leaving.]
sakoman has joined #yocto
Tokamak has joined #yocto
amitk has joined #yocto
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
sakoman has quit [Quit: Leaving.]
goliath has quit [Quit: SIGSEGV]
Lihis has quit [Quit: Quitting]
Lihis has joined #yocto
jsbronder has quit [Ping timeout: 250 seconds]
jsbronder has joined #yocto
camus has quit [Ping timeout: 240 seconds]
camus has joined #yocto
davidinux has quit [Ping timeout: 250 seconds]
davidinux has joined #yocto
camus1 has joined #yocto
camus has quit [Remote host closed the connection]
camus1 is now known as camus
sstiller has joined #yocto
glembo[m] has quit [Quit: Client limit exceeded: 20000]
cperon has quit [Quit: Client limit exceeded: 20000]
Wouter0100 has quit [Remote host closed the connection]
Wouter0100 has joined #yocto
GNUmoon has quit [Ping timeout: 276 seconds]
rob_w has joined #yocto
zpfvo has joined #yocto
camus has quit [Ping timeout: 256 seconds]
camus has joined #yocto
camus1 has joined #yocto
zpfvo has quit [Ping timeout: 240 seconds]
camus has quit [Ping timeout: 240 seconds]
camus1 is now known as camus
zpfvo has joined #yocto
booboo1212[m] has joined #yocto
zpfvo has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
ad__ is now known as kernelspace
mckoan|away is now known as mckoan
<mckoan>
good morning
glembo[m] has joined #yocto
cperon has joined #yocto
GNUmoon has joined #yocto
jmiehe has joined #yocto
Schlumpf has joined #yocto
rfuentess has joined #yocto
ederibaucourt has joined #yocto
gsalazar has joined #yocto
ederibaucourt1 has joined #yocto
ederibaucourt has quit [Quit: Client closed]
ederibaucourt1 has left #yocto [#yocto]
ederibaucourt has joined #yocto
<ziga_>
@Tartarus I did diff them and they look identical. But somehow one boots while other one does not. Is it possible that I have to also set up U-boot properly?
ederibaucourt has left #yocto [#yocto]
ederibaucourt has joined #yocto
ederibaucourt has quit [Client Quit]
ederibaucourt has joined #yocto
ederibaucourt has left #yocto [#yocto]
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
<qschulz>
ziga_: why are you decompiling a dtb?
camus1 has joined #yocto
camus has quit [Ping timeout: 256 seconds]
camus1 is now known as camus
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
mvlad has joined #yocto
rob_w has quit [Quit: Leaving]
zyga-mbp has joined #yocto
goliath has joined #yocto
zpfvo has quit [Ping timeout: 268 seconds]
zpfvo has joined #yocto
camus1 has joined #yocto
florian has joined #yocto
camus has quit [Ping timeout: 240 seconds]
camus1 is now known as camus
zpfvo has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
gsalazar_ has joined #yocto
gsalazar_ has quit [Client Quit]
gsalazar_ has joined #yocto
gsalazar_ has quit [Remote host closed the connection]
gsalazar has quit [Ping timeout: 250 seconds]
<coldspark29[m]>
qschulz: My bugzilla account is ready. In which section should I file the bug? Can't find poky anywhere and the script is a part of poky
<qschulz>
coldspark29[m]: openembedded or bitbake section if there's one
zpfvo has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
<ziga_>
I run "bitbake -c menuconfig u-boot", do some changes and save the resulting .conf file. Then I run "bitbake core-image-minimal" but nothing changes the image inside tmp/work/.../images carries the same date/hour as it's predecessor image. It looks like build system does not register that I changed anything. How do I register my changes?
<qschulz>
ziga_: is u-boot ACTUALLY part of your rootfs?
<qschulz>
or a .wic file?
<qschulz>
because if not, then just u-boot binaries should be updated
<ziga_>
At the end of compilation I get a .wic.xz file which I put to SD carrd with xzcat and I can see the /boot/u-boot.img there.
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
xmn has quit [Quit: ZZZzzz…]
<qschulz>
ziga_: mmmmm
<qschulz>
I assume the issue is that you're not using u-boot but a flavored recipe
<qschulz>
no, let's start with the basics, we'll see later on for that one
camus has quit [Quit: camus]
<qschulz>
you run menuconfig, you take which file exactly from where, then put the file where?
<ziga_>
@qschulz How can I tell if I use flavoured recipe? Something like: "oe-pkgdata-util lookup-recipe u-boot"? I only changed the default devicetree from "am335x-something" to "am335x-something-else" then saved and that was it.
<qschulz>
ziga_: u-boot is the upstream recipe, usually what one does is to use virtual/bootloader instead of u-boot
<qschulz>
so you load the device tree in fdt_addr_r you want and then use bootz
<ziga_>
Okay. First things first. What is "bootz"? :D
<qschulz>
ziga_: `help bootz` in U-Boot
<ziga_>
I don't even know how to get into u-boot prompt...
zpfvo has quit [Ping timeout: 268 seconds]
<qschulz>
ziga_: you might be using extLinux.conf too, there are many different ways to configure the bootloader at runtime
zpfvo has joined #yocto
<qschulz>
ziga_: if configured to allow interaction on the console (the upstream default), any key when you have "Hit any key to stop autoboot:" will bring you into U-Boot's shell
<qschulz>
it is NOT a POSIX shell
<qschulz>
but this has nothing to do with Yocto, at best you might have a variable in your machine configuration file to tell the U-Boot ti recipe which device tree to boot the kernel with
<qschulz>
but that is specific to your board and vendor
<ziga_>
So I flash the SD card, boot from it and keep pressing anything... And it should give me U-boot prompt. Can I use a "bitbake -c menuconfig u-boot-ti-staging" to somehow set up a U-boot "prompt" at boot?
<qschulz>
didn't understand the question
<dwagenk>
@ziga_ you should be able to increase the timeout and adapt the prompt's text in the menuconfig
<ziga_>
Ok. I will try this.
<dacav>
Hi. Quick question about the 'devshell'-like tasks (including 'menuconfig'). Can I avoid having a new shell for it? I know about OE_TERMINAL, but 'none' does not do what I expected :)
<dacav>
I'm wondering if it is possible to have the shell as a subprocess of the one running bitbake
zpfvo has quit [Ping timeout: 268 seconds]
zpfvo has joined #yocto
<Perceval[m]>
Hello all :)
<Perceval[m]>
I encounter a problem in my build, a lot of (not to say all) recipes cannot do the patch task: especially in the sed command on /workspaces/yocto_build_release//sysroots-components/x86_64/quilt-native/fixmepath (for example)
<Perceval[m]>
for example I have
<Perceval[m]>
sed: can't read /workspaces/yocto_build_release//work/x86_64-linux/autoconf-native/2.69-r11/recipe-sysroot-native/usr/bin/quilt: No such file or directory
<Perceval[m]>
and when I do ls /workspaces/yocto_build_release//work/x86_64-linux/autoconf-native/2.69-r11/recipe-sysroot-native/
<Perceval[m]>
there is only installeddeps and sysroots-components
<Perceval[m]>
it is only in /workspaces/yocto_build_release//work/x86_64-linux/autoconf-native/2.69-r11/recipe-sysroot-native/sysroots-components/x86_64/quilt-native/ that if found
<Perceval[m]>
etc sysroot-providers usr/bin/quilt
<dacav>
Perceval[m]: I'm still quite noob but ...could it be that you need to declare it as a build-time dependency?
<dacav>
DEPENDS = " ... "
<Perceval[m]>
the build was running fine juste before I upgrade my depencies (as submodules) to the latest commits of their respective branches. I manage to build the image already I just have this bug that popped from nowhere ><
zpfvo has quit [Ping timeout: 268 seconds]
<Perceval[m]>
dacav: and I manage to build the image a first time after the upgrades, so it shouldn't be a dependencies problem
<dacav>
It sounds weird that you managed to complete a build, with a failing do_patch
<Perceval[m]>
the patches were not failing in the previous build
<Perceval[m]>
that's why it is weird 😅
zpfvo has joined #yocto
<dacav>
...could it be that the image you see is cached, and that the current build fails because of the do_patch failure?
zpfvo has quit [Ping timeout: 256 seconds]
<dacav>
Also, I wonder if dropping some build directories might work
<Perceval[m]>
I deleted sstate cache and tmp directories in order to restart the build from the beginning but still.
<Perceval[m]>
It seems to have a relation to how sysroots and native sysroots are handled
<Perceval[m]>
dacav: so the caches are out of scope for this one 😊
zpfvo has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
JaMa has joined #yocto
<dacav>
rburton: thanks. I was afraid so :) ...well, it is a minor problem, as you can guess.
<dacav>
Perceval[m]: sorry, no other idea from me :) I'm not experienced enough, I'm afraid
Schlumpf has quit [Quit: Client closed]
Tyaku has joined #yocto
codavi has joined #yocto
Michael80 has joined #yocto
<Michael80>
Hello, I am trying to use Eclipse 2021-12 to build code for my target device. I have configured Yocto, built an image, run this image on my device and run the bitbake populate_sdk command. I installed the sdk using the .sh file. Can anyone speak with my about the error I am seeing while configuring eclipse?
<qschulz>
and saw it was fixed in a 5.1x something branch and misread 2 for 5 :/
Michael57 has quit [Quit: Client closed]
zpfvo has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
sstiller has quit [Quit: Leaving]
zpfvo has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
<smurray>
qschulz: AIUI some of the concern when they announced the changes in that blog post were fixes for LTS branches wouldn't become available to non-customers until they decided to do a point release
<smurray>
qschulz: so it seems possible that Qt co has a fix that only customers have gotten so far :/
<smurray>
qschulz: though I guess that CVE links to some commits in their repo
<svuorela>
qschulz, smurray: KDE has a large collection of many of such patches.
rfuentess has quit [Remote host closed the connection]
alessioigor has quit [Client Quit]
lucaceresoli has quit [Quit: Leaving]
leon-anavi has quit [Remote host closed the connection]
Tokamak has quit [Read error: Connection reset by peer]
Tokamak has joined #yocto
florian_kc has quit [Ping timeout: 240 seconds]
stephano is now known as stephano[away]
stephano[away] is now known as stephano
winfried has joined #yocto
<winfried>
Hi, I'm writing a recipe for package hardening-check, builds with only a simple Makefile. The recipe installs script hardening-check.
<winfried>
I would like to include this package in our SDK so I added line BBCLASSEXTEND = "native nativesdk" to the recipe.
<winfried>
bitbake hardening-check runs fine
<winfried>
and bitbake hardening-check-native as well
stephano is now known as stephano[away]
<winfried>
But when I add 'hardening-check-native' to IMAGE_INSTALL than the build of that image fails with:
<winfried>
Task do_populate_sdk in <myimage.bb> rdepends upon non-existent task do_package_write_rpm in virtual:native:(...)/hardening-check_2.6.bb
<winfried>
Any ideas what I do wrong ?
florian_kc has joined #yocto
winfried has quit [Quit: Client closed]
florian_kc has quit [Ping timeout: 240 seconds]
<dwagenk>
<winfried> "But when I add 'hardening-check..." <- the `-native` package in `IMAGE_INSTALL` looks wrong, native recipes shpuldn't be part of the image. To have it in the SDK look at the docs for TOOLCHAIN_HOST_TASK.
perdmann has quit [Quit: leaving]
Minvera has joined #yocto
dev1990 has joined #yocto
osama has joined #yocto
<ziga_>
I install "vim" on my image with IMAGE_INSTALL += "vim" but whenever I starrt "vim" I get a warning "terminal capability "cm" required" and interface is displayed in a wrong way.
<ziga_>
How can this be solved?
<ziga_>
Ah! I just exported TERM = xterm and now it works.
osama is now known as smsm
goliath has quit [Quit: SIGSEGV]
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
florian_kc has joined #yocto
stephano[away] is now known as stephano
Tokamak has joined #yocto
Tokamak has quit [Ping timeout: 250 seconds]
florian_kc has quit [Ping timeout: 240 seconds]
<vd>
does recipes-core historically referred to the "core" layer (openembedded-core/meta) or simply refers to what's core to the layer?
stephano is now known as stephano[away]
Tokamak has joined #yocto
amitk_ has joined #yocto
alejandrohs has quit [Ping timeout: 256 seconds]
alejandrohs has joined #yocto
amitk has quit [Ping timeout: 256 seconds]
<rburton>
vd the latter
<vd>
thank you
<vd>
in some scenarios, I need to hammer a few images, like removing the kernel from the rootfs if present, adding or removing some packages, etc. What's the best way to do that?
stephano[away] is now known as stephano
Michael17 has joined #yocto
<vd>
require recipes-core/images/some-generic-image.bb and a few IMAGE_INSTALL:remove = " foo" in recipes-core/images/hammered-image.bb?
<Michael17>
Can we build and debug code using eclipse?
<Michael17>
I can not seem to get this working
Minvera has quit [Quit: Leaving]
smsm has quit [Ping timeout: 256 seconds]
osama has joined #yocto
sakoman has quit [Quit: Leaving.]
<zeddii>
Michael17: eclipse support hasn't really worked for quite a while. No one was supporting the integration.
<Michael17>
Is there a work around? A way to debug my code on target?