Telgareith has quit [Read error: Connection reset by peer]
Telgareith9 has joined #yocto
seninha has quit [Quit: Leaving]
prabhakarlad has quit [Quit: Client closed]
nemik has quit [Ping timeout: 244 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
sakoman has quit [Quit: Leaving.]
seninha has joined #yocto
starblue has quit [Ping timeout: 268 seconds]
starblue has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 244 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 244 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
alex88 has quit [Ping timeout: 252 seconds]
zeddii has quit [Ping timeout: 244 seconds]
sakoman has joined #yocto
Guest2237 has quit [Quit: Client closed]
jclsn has quit [Ping timeout: 264 seconds]
jclsn has joined #yocto
alex88 has joined #yocto
CobaltBlue has joined #yocto
amitk has joined #yocto
seninha has quit [Remote host closed the connection]
tarxf has joined #yocto
GNUmoon2 has quit [Remote host closed the connection]
GNUmoon2 has joined #yocto
sakoman has quit [Quit: Leaving.]
ardo has quit [Read error: Connection reset by peer]
ardo has joined #yocto
pgowda_ has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
camus has quit [Ping timeout: 252 seconds]
camus has joined #yocto
paowz has joined #yocto
xmn has quit [Ping timeout: 264 seconds]
rob_w has joined #yocto
alessioigor has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
davidinux has quit [Ping timeout: 252 seconds]
davidinux has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
eirikb has quit [Ping timeout: 252 seconds]
rfuentess has joined #yocto
nemik has quit [Ping timeout: 244 seconds]
zpfvo has joined #yocto
nemik has joined #yocto
frieder has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
Schlumpf has joined #yocto
goliath has quit [Quit: SIGSEGV]
mckoan|away is now known as mckoan
<mckoan>
good morning
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
denisoft81 has joined #yocto
<qschulz>
mckoan: o/
tre has joined #yocto
eirikb has joined #yocto
zpfvo has quit [Quit: Leaving.]
zpfvo has joined #yocto
* alessioigor
waves all
prabhakarlad has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
florian has joined #yocto
dacav has quit [Quit: leaving]
dacav has joined #yocto
denisoft81 has quit [Remote host closed the connection]
goliath has joined #yocto
ardo has quit [Read error: Connection reset by peer]
ardo has joined #yocto
<frieder>
Is there some way to append/prepend an existing anonymous python function in a recipe?
frank_smith has joined #yocto
<frank_smith>
Hi, I would like to prevent compiling and deploying the kernel-modules with "_remove". I am using yocto dunfell with linux-fslc.
<frank_smith>
MACHINE_EXTRA_RRECOMMENDS_remove = "kernel-modules" in my conf file has no effect.
<frank_smith>
BAD_RECOMMENDATIONS = "kernel modules" works, but doesn't seem like the right solution to me?!
<frank_smith>
MODULE_TARBALL_DEPLOY = "0" only prevents deploying, but not compiling.
<frank_smith>
In the task-depends.dot I see that the only dependency is on the kernel itself.
<qschulz>
frieder: IIRC you can have multiple anonymous functions in a recipe?
<qschulz>
frank_smith: find where the kernel-modules package is pulled in your image and remove it from there
eirikb has quit [Quit: Client closed]
<qschulz>
the kernel modules will always be compiled. If you don't want modules compiled, modify your defconfig to not have any module to build?
<qschulz>
to be more precise, kernel-modules is just a package of the kernel recipe
<qschulz>
you very likely need a kernel for your machine, so once the kernel recipe is built, you'll have the kernel package and the kernel-modules package
<qschulz>
kernel-modules package does not add build time to your build per se
<frieder>
qschulz: Indeed, I just found out that adding them in the right order seems to work fine. Thanks!
<frank_smith>
qschulz: Thanks for explaining . Any hint on how to find the pulling recipe?
<landgraf>
frank_smith: bitbake -g <your_image>
<landgraf>
frank_smith: and then take a look into `task-dep*` file in the build directory.
JohnSmith[m] has quit [Quit: You have been kicked for being idle]
Guest2237 has joined #yocto
odra has joined #yocto
florian_kc has joined #yocto
zpfvo has quit [Ping timeout: 268 seconds]
ente` has quit [Ping timeout: 264 seconds]
zpfvo has joined #yocto
eirikb has joined #yocto
starblue has quit [Ping timeout: 268 seconds]
starblue has joined #yocto
ente` has joined #yocto
rfuentess has quit [Remote host closed the connection]
<chrysh>
Hello! Is it tolerated to put binaries into the files folder of a recipe, or is it highly discouraged? If yes, why?
<rburton>
discouraged, for sure.
<rburton>
A layer should be metadata and patches, not binaries which presumably needed to be built at some point. How are they rebuilt?
prabhakarlad has quit [Quit: Client closed]
<sotaoverride>
Im trying to run the latest ca-certificates with openssl_1.0.2u and keep getting the rehash is an invalid command error. Ive tried patching ca-certificates to use c_rehash and certhash instead, but nothing has worked. Some one tell me how to figure this out. Also how do I figure out what rehash alternative commands have I got in my sysroot?
<eirikb[m]>
Can I disable systemd from my image?
<landgraf>
you can
<sotaoverride>
eirikb[m]: yeha just make sure your image recipe / distro doesnt include it?
<qschulz>
eirikb[m]: probably not, it needs to be a distro configuration
<eirikb[m]>
sotaoverride: Distro includes it, but I would like to create an image without it
<qschulz>
eirikb[m]: just guessing here but you have an initramfs you want to be minimal which then does a switchroot or something to a full featured rootfs with systemd?
ptsneves has joined #yocto
pgowda_ has quit [Quit: Connection closed for inactivity]
<eirikb[m]>
qschulz: I just want the image without systemd. It will run in docker
prabhakarlad has joined #yocto
<qschulz>
eirikb[m]: then you "just need to select the correct init system"
<qschulz>
by specifying in your distro which one to use
<eirikb[m]>
qschulz: I can have multiple? I want systemd in every other image, just not in this one because it will run in docker
<qschulz>
eirikb[m]: I'm afraid no
<eirikb[m]>
Can I have multiple distros then? I'm not the author of this setup, and I don't know much about Yocto
<qschulz>
eirikb[m]: of course you can!
<qschulz>
you select a distro by setting the DISTRO variable in your local.conf
florian_kc has quit [Ping timeout: 248 seconds]
xmn has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
Tokamak has quit [Ping timeout: 255 seconds]
<eirikb[m]>
<qschulz> "you select a distro by setting..." <- Looks like this could work. I'm getting errors about busybox, seems it requires systemd. I don't need busybox as far as I know, but not sure how to not have it, or where it comes from. Not in the image bb-file at least
<qschulz>
eirikb[m]: probably modified recipe or a bbappend for busybox because i'm pretty sure I'm using busybox and I've never had a distro with systemd :)
<eirikb[m]>
Something somewhere for sure. A lot of files here...
Tokamak has joined #yocto
prabhakarlad has quit [Quit: Client closed]
zpfvo has quit [Ping timeout: 252 seconds]
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
Piraty_ has quit [Quit: -]
Piraty has joined #yocto
<wyre>
hi guys, I'm trying to boot my image from nfs ... but cannot get properly working because of apparently the root filesystem is not mounted as rw, systemd doesn't work properly, but I finally booted a debug shell and I can see strange things like these https://bpa.st/T6SA
<wyre>
why do you think is this? the root fs is apparently mounted as rw
prabhakarlad has joined #yocto
<bigendian>
what are best options to run Yocto on windows ? Virtualbox is one, but is there any other valid opion ?
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
frank_smith has joined #yocto
<rburton>
bigendian: WSL2
frank_smith has quit [Client Quit]
<wyre>
bigendian, you mean bitbake?
zpfvo has joined #yocto
<wyre>
bigendian, I use the crops/poky docker image to create a custom container where I'm able to properly run bitbake 😉
<wyre>
if you have docker installed ... you can just do docker pull crops/poky and you will have the image
sakoman has joined #yocto
tre has quit [Remote host closed the connection]
rob_w has quit [Quit: Leaving]
<eirikb[m]>
<qschulz> "eirikb: probably modified recipe..." <- I gave up. It was mostly to keep it cleaner and have the init scripts for sshd, not a big deal. It will have systemd, but never run it
kscherer has joined #yocto
Guest2237 has quit [Ping timeout: 252 seconds]
alessioigor has quit [Quit: alessioigor]
nemik has quit [Ping timeout: 244 seconds]
nemik has joined #yocto
<bigendian>
rburton: thanks
<bigendian>
wyre: isn't docker stuff linux only ?
nemik has quit [Ping timeout: 264 seconds]
nemik has joined #yocto
Tokamak has quit [Ping timeout: 260 seconds]
<wyre>
bigendian, I think there is also a docker version for windows
sgw has quit [Quit: Leaving.]
<wyre>
but still not sure if you meant to run yocto images or to build yocto images 😊
sgw has joined #yocto
<rburton>
docker exists for windows/mac/linux
Tokamak has joined #yocto
vladest has quit [Remote host closed the connection]
Piraty has quit [Quit: -]
prabhakarlad has quit [Quit: Client closed]
goliath has quit [Quit: SIGSEGV]
Schlumpf has quit [Quit: Client closed]
Piraty has joined #yocto
zpfvo has quit [Ping timeout: 240 seconds]
<chrysh>
rburton: Ok, then I will need to fix it at some point. My problem right now is that the expected cmake version to build the static library is higher than whatever I have in the vendor bsp, and as far as I understand upgrading something like compiler or cmake version in yocto is always a pita
prabhakarlad has joined #yocto
Minvera has joined #yocto
<rburton>
JaMa: replied to your insane/poison thing, I've a hunch your distro is doing something unexpected.
Tokamak has quit [Ping timeout: 255 seconds]
<sotaoverride>
can someone explain how sysroots work? Does every recipe set up its own sysroot or what?
<RP>
rburton: that discussion didn't seem to add up to me but I couldn't tell why
zpfvo has joined #yocto
<rburton>
sotaoverride: yes
Tokamak has joined #yocto
<rburton>
sotaoverride: as seen in the work directory: recipe-sysroot and recipe-sysroot-native
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
<JaMa>
rburton: it's reproducible with nodistro oe-core build, so there is no "my" distro nor my gcc-cross
<rburton>
so if i build boost, i should find that warning in my log?
<JaMa>
I believe so
<JaMa>
I've triggered the same to share the full log
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
<sotaoverride>
rburton: for some reason I dont see any sysroots under work, just a bunch of run.do_prepare_recipe_sysroot
<sotaoverride>
no actual directories
<rburton>
the paths are tmp/work/[tune]/[recipe]/[version]/recipe-sysroot
<rburton>
in your example, why is boost searching /usr in the first place
<rburton>
ah
<rburton>
well i suspect that is because its finding python3-dev on your host
<rburton>
my build has -I"." -I"/yocto/ross/build/tmp/work/cortexa57-poky-linux/boost/1.80.0-r0/recipe-sysroot/usr/include/python3.10" -c
<rburton>
your boost log has -I"/usr/include" -c
<rburton>
can you check your configure log to see if that's correct?
<rburton>
obviously *that* should have also thrown an error
<sotaoverride>
ok, so It seems like c_rehash does make its way to sysroot, then why does ca-certificate complain that c_rehash is an invalid command? I patch ca-certificates to use c_rehash instead of rehash. and this is where I see c_rehash sitting: ./dragonboard_410c-linaro-linux/rpb-bi-image/1.0-r0/recipe-sysroot-native/usr/bin/c_rehash
<rburton>
whats the context here
<sotaoverride>
ok so Im using opensll1.0.2u and trying to make it work with the latest ca-certificates. During that process ca-certificates started complaing that rehash is a command it cant find. I figured I could patch ca-certificates to use c_rehash instead. For some reason neither works. c_rehash, rehash, and even certhash...
<sotaoverride>
youd see it erroring out with openssl:Error: 'certhash' is an invalid command.
<JaMa>
rburton: my build is still running (together with some other builds on background), but you're probably right about python-dev, because it doesn't seem reproducible with ubuntu host, but it's triggered on gentoo
<JaMa>
rburton: and command line args don't seem to affect it as well as it is still just warning with this minimized call https://pastebin.com/h7mu3eQ6
<rburton>
JaMa: can you verify that oe-selftest -r buildoptions.Poisoning fails?
frieder has quit [Remote host closed the connection]
<rburton>
i've "fixed" poison.bb so it doesn't break which breaks the test suite now
<rburton>
but now need to cook
<JaMa>
ah it was using CPP (so with -E), but why it failed with nodistro might be some separate issue (as I normally don't use selftest with oe-core/nodistro)
Tokamak has quit [Ping timeout: 260 seconds]
Ad0 has quit [Ping timeout: 252 seconds]
Tokamak has joined #yocto
Ad0 has joined #yocto
florian_kc has joined #yocto
<JaMa>
ok, in oe-core/nodistro buildoptions.Poisoning failed, because res.output was "/bin/sh: line 1: bitbake: command not found"
goliath has joined #yocto
florian_kc has quit [Ping timeout: 244 seconds]
msgboardpana[m] has joined #yocto
msgboardpana[m] is now known as kiwi_29_[m]
odra_ has joined #yocto
odra has quit [Read error: Connection reset by peer]
Tokamak has quit [Ping timeout: 244 seconds]
Tokamak has joined #yocto
Tokamak_ has joined #yocto
Tokamak has quit [Ping timeout: 255 seconds]
<rburton>
huh
Tokamak_ has quit [Ping timeout: 244 seconds]
Tokamak has joined #yocto
vladest has joined #yocto
<khem>
sotaoverride: perhaps run c_rehash during build of ca-certificates to generates needed links so you dont need to regenerate them during runtime
<kiwi_29_[m]>
Hello, I am trying to compile a package with Makefile which does not have install target inside. This is a third party package. so at the end of compile using yocto, I get this error *** No rule to make target 'install'. Stop.
<kiwi_29_[m]>
I am inheriting autotools in side recipe and calling autotools_do_install in do_install in recipe
<rburton>
khem: see above chat between me and jama. our gcc-poison-system-directories patch doesn't work for compile jobs. any obvious issues given recent gcc changes?
<kiwi_29_[m]>
* Hello, I am trying to compile a package with Makefile which does not have install target inside. This is a third party package. so at the end of compile using yocto, I get this error \*\*\* No rule to make target 'install'. Stop.
<kiwi_29_[m]>
I am inheriting autotools in side recipe and calling autotools\_do\_install in do\_install in recipe
<kiwi_29_[m]>
How to make sure the installation succeeds..thanks
<rburton>
kiwi_29_[m]: first, don't inherit autotools if it doesn't use autotools
<kiwi_29_[m]>
* Hello, I am trying to compile a package with Makefile which does not have install target inside. This is a third party package. so at the end of compile using yocto, I get this error *** No rule to make target 'install'. Stop.
<kiwi_29_[m]>
I am inheriting autotools in side recipe and calling autotools_do_install in do_install in recipe.
<kiwi_29_[m]>
How to make sure the installation succeeds..thanks
<rburton>
if it doesn't have an install target then you need to do the install manually. write a do_install() that uses the install command to copy files from the build tree into eg ${D}${bindir}
<kiwi_29_[m]>
rburton: I see.. so directly call make inside recipe?
<rburton>
the default do_compile() will call make for you
<kiwi_29_[m]>
rburton: But I have to cd to source dir inside do_compile (it is a GO lang source which creates additional subdirs where git clone happens).. so default do_compile does not exist
<rburton>
if it's a go package then there are go classes
<rburton>
(so much easier if you can point to the source you're building)
<kiwi_29_[m]>
so just inherit go is needed ..right
<kiwi_29_[m]>
* needed ..right?
<rburton>
if it builds with go install
Tokamak_ has joined #yocto
Tokamak has quit [Ping timeout: 255 seconds]
<rburton>
JaMa: so i think the bug is with the defaults specs in gcc
Tokamak has joined #yocto
Tokamak_ has quit [Ping timeout: 244 seconds]
odra_ has joined #yocto
odra_ has quit [Remote host closed the connection]
odra_ has joined #yocto
<rburton>
so i think i misread a comment in gcc
<rburton>
JaMa: have a fix, i hope. scared to do a build...
<rburton>
RP: this might have an annoyingly bad fallout
<kiwi_29_[m]>
cool.. rburton .. I am able to compile and install .. not it is QA issue --> File from recipe was already stripped, this will prevent future debugging! [already-stripped]
<kiwi_29_[m]>
* cool.. rburton .. I am able to compile and install .. now it is QA issue --> File from recipe was already stripped, this will prevent future debugging! \[already-stripped\]
<rburton>
ideally, stop the makefile from stripping
<rburton>
if you can't, look up INSANE_SKIP in the manual
odra_ has quit [Read error: Connection reset by peer]
ardo has quit [Read error: Connection reset by peer]
<RP>
rburton: we'll just have to work through it. I didn't read all the scrollback but I can guess :/
zeddii has joined #yocto
ardo has joined #yocto
odra__ has quit [Ping timeout: 244 seconds]
* zeddii
is finally back online.
<zeddii>
two weeks of vacation, followed by construction work cutting my cable connection, and 5 days of being offline.
<zeddii>
good times
<zeddii>
if anyone has pinged me on here for 2 1/2 weeks, I didn't see it.
<RP>
zeddii: welcome back. I thought you'd been quiet! :)
<rburton>
JaMa: success!
<rburton>
JaMa: poky-contrib:ross/poison, please do test. I'm going to build the world and hope nothing explodes!
<RP>
rburton: I like the branchname :)
<rburton>
cross your fingers
<RP>
rburton: will do!
<zeddii>
RP: I had some email access, but was running over a phone usb tether for my access. so I couldn't do builds, or work on anything.
<zeddii>
since I don't have a data plan that can handle that.
<RP>
zeddii: fair enough. Probably good to get a break anyway
<RP>
can someone break my internet connection? :)
florian_kc has quit [Ping timeout: 252 seconds]
<zeddii>
now I have about 70 things to catch up on. Maybe I can help you with some of those bugs you mentioned previously. since I'm now not going to dublin, I have time.
<rburton>
awww
amitk has quit [Ping timeout: 244 seconds]
<RP>
zeddii: the good news is I think the worst of the bugs are under control. If we can sort the remaining rust issue (which is now just a license issue on a file) then I can attempt to build M3 finally
<zeddii>
ack'd. well, least I'm around now to catch up on kernel stuff, fixup meta-virt and lend a hand with anything else that pops up.
<RP>
zeddii: thanks, I'm sure something will explode, it did repeatedly last week!
* RP
is sure the autobuilder noticed when people are on vacation
<RP>
zeddii: actually there is one thing I'd like an opinion on. There is a kernel build change in master-next which I'm thinking I'd prefer to drop
<RP>
zeddii: it has risk with it, but it probably does fix a bug :/
<zeddii>
RP: ok, let me have a look. is that the one where you put the same flags everywhere, or something else ?
<RP>
zeddii: no, I merged the flags ones. This is one from Jose
<RP>
zeddii: the flags ones should be safe and if they break something we probably want to know
<zeddii>
ok. let me bring up my servers again, and check master-next
<zeddii>
I have a bunch of -stable kernel changes, I'll rebuild them now and send the queue once it looks ok.
<RP>
zeddii: ideally I want to simplify the kernel intertask dependencies, this patch complicates things further
<rburton>
thankfully they backported trivially, i really didn't want to spend more than ten minutes
<zeddii>
I hear you on that!
<zeddii>
RP: I see the change, I remember not seeing the point of it when it was posted to the list.
nemik has quit [Ping timeout: 268 seconds]
<RP>
zeddii: staring at the code I think I could maybe see it but I've paged it out since I last looked
nemik has joined #yocto
<zeddii>
I mean, it should work, and anything depending on the shared_workdirs already has a long dependency to wait for.
<zeddii>
but this of course makes it even longer.
<RP>
zeddii: right, the performance aspect puts me off a lot :(
<zeddii>
it's unclear to me why we need the new task, and why not just move do_shared_workdir after do_compile_kernelmodules ?
<zeddii>
and anything that has a race, or cares, should change its dependency to after do_compile_kernelmodules to opt into the longer dependency
<RP>
zeddii: right, I wondered about that too
<RP>
zeddii: it was a patch I didn't merge as it needed more investigation
Tokamak has quit [Ping timeout: 255 seconds]
<zeddii>
so yah. I can follow up to the list and ask some questinos, but those really aren't things that jose can answer, since he wouldn't have looked at it from that point of view either.
kscherer has quit [Quit: Konversation terminated!]
<RP>
zeddii: I think we do need to do that and then try and work things out. I'm going to drop it until we have more answers though
Tokamak has joined #yocto
<zeddii>
ack'd. I'll do a reply in a bit, while you finally log off for the night!
odra__ has joined #yocto
<RP>
zeddii: Thanks. I have a migraine coming on :/
Tokamak_ has joined #yocto
Tokamak has quit [Ping timeout: 260 seconds]
Minvera has quit [Remote host closed the connection]
odra_ has joined #yocto
odra__ has quit [Read error: Connection reset by peer]
<rburton>
RP: time to log off!
<RP>
rburton: I was away for a few hours and it has been hovering the whole time
<JaMa>
rburton: surprisingly -I"/usr/include" disappeared in boost log.do_compile now even when icu is detected
<JaMa>
rburton: because poison prevents host's icu to be detected http://dpaste.com/HWEL5UWPR in ./libs/regex/build/Jamfile.v2 ./libs/locale/build/Jamfile.v2
justache is now known as justache_test
justache_test is now known as justache
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
goliath has joined #yocto
GNUmoon2 has quit [Ping timeout: 258 seconds]
florian_kc has joined #yocto
florian_kc has quit [Ping timeout: 260 seconds]
GNUmoon2 has joined #yocto
<rburton>
JaMa: that’s the intention: by making it fatal, configure checks fail
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
GNUmoon2 has quit [Remote host closed the connection]