ndec changed the topic of #yocto to: "Welcome to the Yocto Project | Learn more: https://www.yoctoproject.org | Join us or Speak at Yocto Project Summit (2022.05) May 17 - 19, more: https://yoctoproject.org/summit | Join the community: https://www.yoctoproject.org/community | IRC logs available at https://www.yoctoproject.org/irc/ | Having difficulty on the list or with someone on the list, contact YP community mgr ndec"
sakoman has joined #yocto
foxxesStar has quit [Ping timeout: 260 seconds]
qschulz has quit [Remote host closed the connection]
Wouter01001 has quit [Remote host closed the connection]
Wouter01001 has joined #yocto
qschulz has joined #yocto
foxxesStar has joined #yocto
Wouter01001 has quit [Ping timeout: 268 seconds]
Wouter01001 has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
seninha has joined #yocto
MitchGaines has quit [Remote host closed the connection]
starblue has quit [Ping timeout: 256 seconds]
starblue has joined #yocto
Wouter01001 has quit [Read error: Connection reset by peer]
Wouter01001 has joined #yocto
Wouter01001 has quit [Read error: Connection reset by peer]
seninha has quit [Quit: Leaving]
Wouter01001 has joined #yocto
Wouter01001 has quit [Ping timeout: 264 seconds]
fray has quit [Ping timeout: 240 seconds]
Wouter01001 has joined #yocto
fray has joined #yocto
sakoman has quit [Quit: Leaving.]
pgowda_ has joined #yocto
peoliye has quit [Quit: Client closed]
amitk has joined #yocto
kroon has joined #yocto
amitk has quit [Remote host closed the connection]
amitk has joined #yocto
thomasd13 has joined #yocto
gsalazar_ has joined #yocto
gsalazar has quit [Ping timeout: 256 seconds]
alessioigor has joined #yocto
Wouter01001 has quit [Remote host closed the connection]
Wouter01001 has joined #yocto
alessioigor has quit [Quit: alessioigor]
rob_w has joined #yocto
jclsn has joined #yocto
frieder has joined #yocto
goliath has joined #yocto
mvlad has joined #yocto
florian has joined #yocto
rfuentess has joined #yocto
gsalazar_ has quit [Quit: Leaving]
gsalazar has joined #yocto
ptsneves has joined #yocto
florian has quit [Ping timeout: 260 seconds]
davidinux has quit [Ping timeout: 268 seconds]
davidinux has joined #yocto
vladest has quit [Quit: vladest]
twnqx has joined #yocto
mckoan|away is now known as mckoan
vladest has joined #yocto
<ykrons> Hi all
<mckoan> good morning
<ykrons> I'm using Dunfell based BSP from Toradex. My build is failing due to a missing provider for a given recipe because the recipe is not compatible with my machine. I would like to debug looking at the environment with "bitbake -e ..." but as the recipe is not compatible I get nearly no details. What is the proper way to troubleshoot such issue?
<mckoan> ykrons: what is the recipe name ?
ahs3[m] has quit [Quit: You have been kicked for being idle]
violet has quit [Quit: leaving]
violet has joined #yocto
<ykrons> mckoan: cpuburn-a53. I'm including the colibri-imx8x machine to my own and now I'm facing that issue.
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
<mckoan> ykrons: plastebin the error
<rburton> ykrons: if the recipe won't parse because it's not compatible then the problem is a COMPATIBLE_* variable in the recipe. just open the recipe and see.
<rburton> ie cpuburn-arm in meta-oe has COMPATIBLE_MACHINE with dubious restrictions http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-benchmark/cpuburn/cpuburn-arm_git.bb?h=master
<ykrons> mckoan: Just get this "ERROR: Nothing PROVIDES 'cpuburn-a53' cpuburn-a53 was skipped: incompatible with machine 1388-imx8x (not in COMPATIBLE_MACHINE)"
<rburton> so yeah extend COMPATIBLE_MACHINE
<rburton> if you think it should be compatible with your machine
<ykrons> I just found my error, I haven't properly set MACHINEOVERRIDES in my machine :/
nemik has quit [Ping timeout: 268 seconds]
<ykrons> I have written 'MACHINEOVERRIDES =. "colibri-imx8x"' rather that 'MACHINEOVERRIDES =. "colibri-imx8x:"'. Missed the trailing :
nemik has joined #yocto
<mckoan> ykrons: good!
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
<LetoThe2nd> yo dudX
<mihai> yo
<rfuentess> LetoThe2nd: thanks for the talk from yesterday. I'm starting to catch some issues we were having as bad practice in our cmakes xD
<LetoThe2nd> rfuentess: you're welcome, have fun!
starblue has quit [Ping timeout: 240 seconds]
starblue has joined #yocto
ptsneves38 has joined #yocto
ptsneves38 has quit [Client Quit]
ptsneves86 has joined #yocto
ptsneves has quit [Ping timeout: 252 seconds]
hcg has joined #yocto
rfuentess has quit [Read error: Connection reset by peer]
ptsneves86 has quit [Quit: Client closed]
ptsneves has joined #yocto
<ptsneves> rburton in you mention that some patches are in  poky-contrib:ross/nfs. Where is this poky-contrib repo?
<rburton> ptsneves: git.yoctoproject.org
<ptsneves> thanks. Did not know poky-contrib existed
dmoseley_ has quit [Quit: ZNC 1.8.2 - https://znc.in]
hcg has quit [Ping timeout: 252 seconds]
<ptsneves> is there any way to know which yocto release a patch first came in?
<rburton> find the patch in git, then git tag --contains <sha>
<rburton> the github mirror shows you that in the browser
<ptsneves> thanks! the github one is cool for fast perusal
<rburton> all our releases are tagged yocto-* for ease
dmoseley has joined #yocto
<landgraf> git tag --contains $(git log --pretty=format:"%h" --follow <patch_file) | tail -n1 )
dmoseley has quit [Quit: ZNC 1.8.2 - https://znc.in]
dmoseley has joined #yocto
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
rfuentess has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
rfuentess_ has joined #yocto
rfuentess has quit [Ping timeout: 255 seconds]
rfuentess__ has joined #yocto
rfuentess_ has quit [Ping timeout: 246 seconds]
MitchGaines has joined #yocto
Tyaku has joined #yocto
vvn has quit [Ping timeout: 272 seconds]
vvn has joined #yocto
davidinux has quit [Ping timeout: 264 seconds]
rfuentess__ is now known as rfuentess
ruslan has joined #yocto
<ruslan> Hello! I added meta-openembedded/meta-webserver layer in bblayers.conf. Also I added distro features:
<ruslan> DISTRO_FEATURES:append = " pam systemd "
<ruslan> But I'm getting error:
<ruslan> ERROR: Nothing RPROVIDES 'cockpit' (but /home/user/Projects/poky-rpi/rpi-build/../meta-openembedded/meta-webserver/recipes-core/packagesgroups/packagegroup-meta-webserver.bb RDEPENDS on or otherwise requires it)
<ruslan> cockpit was skipped: missing required distro features 'pam systemd' (not in DISTRO_FEATURES)
<ruslan> Part of my bb recipe: https://bpa.st/66YA
jpuhlman has quit [Remote host closed the connection]
<rburton> ruslan: where did you add DISTRO_FEATURES:append?
<rburton> distro features are distro-wide, so need to be in local.conf or your own distro configuration file if you have one
<rburton> putting it in an image recipe will change it *for that recipe*, not the cockpit recipe
<ruslan> rburton: In image recipe
<rburton> LetoThe2nd's first rule of yocto: variables set in a recipe, stay in the recipe
<ruslan> rburrton: thanks, got it
Guest17 has joined #yocto
<Guest17> Hi, how do I add the systemd-coredump  service to my own yocto distro? Is there a IMAGE_INSTALL_append string I must add?
<Guest17> DISTRO_FEATURES already contains "systemd"
<Guest17> but there is no such service systemd-coredump in my bitbaked yocto distro by default
<rburton> that service isn't on by default
<rburton> see the recipe: it has a packageconfig for coredump but it's not enabled
<rburton> https://docs.yoctoproject.org/ref-manual/variables.html#term-PACKAGECONFIG talks about how to turn on packageconfigs
<Guest17> hey cool. Thank you
xenador77 has joined #yocto
davidinux has joined #yocto
jpuhlman has joined #yocto
seninha has joined #yocto
<Guest17> I can't find where a recipe for the systemd is and where a packageconfig is set disabled there
<Guest17> Can you point my to a path and file, plz?
<ruslan> I don't know for sure, but may be this? meta/recipes-core/systemd/systemd_250.5.bb
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
<Guest17> ah OK. I suppose, I must create a file recipes-core/systemd/systemd_244.3.bb_append  file here and overrule this variable:    PACKAGECONFIG[coredump] = "-Dcoredump=true, -Dcoredump=false"
<Guest17> right?
<Guest17> I  mean "-Dcoredump=true"
<rburton> no, reread the docs :)
<ernstp> Guest17: bitbake-layers show-recipes -f systemd
<Guest17> I don't get it as I'm reading that docs chapter
<ruslan> Guest17: You may do it this way:
<ruslan> create systemd_%.bbappend file and add the following line there:
<ruslan> PACKAGECONFIG:append = " coredump "
<Guest17> ruslan: I see! That's a good example. Thank you :-)
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
kscherer has joined #yocto
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
rob_w has quit [Remote host closed the connection]
sakoman has joined #yocto
kroon has quit [Quit: Leaving]
amitk has quit [Ping timeout: 255 seconds]
sakoman has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
sakoman has joined #yocto
armhzjz has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
<armhzjz> Can I have docker-compose in my final yocto image? I managed to build docker-ce, but I'd like to also have docker-compose and don't see a recipe for it
nemik has joined #yocto
<armhzjz> Thanks rburton
<armhzjz> I had seen the recipe locally but didn't understand it. I was expecting to see a recipe downloading the docker-compose binaries or something alike
<armhzjz> I'll give it a try
<rburton> yocto never reuses existing binaries, we also build our own
prabhakarlad has quit [Quit: Client closed]
<armhzjz> oh I see
thomasd13 has quit [Ping timeout: 255 seconds]
<ptsneves> has anybody ever seen issues of undefined references to libatomic symbols, like in armv5?
<vmeson> ptsneves: do you have the exact string?
DougC has quit [Quit: Client closed]
rfuentess_ has joined #yocto
rfuentess has quit [Ping timeout: 264 seconds]
Guest17 has quit [Ping timeout: 252 seconds]
<ptsneves> src/libntirpc.so.4.0: undefined reference to `__atomic_fetch_add_8'
<ptsneves> vmeson i guess it is related to this https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358
<ptsneves> which is a "known" kind of wont fix
<ptsneves> i am just a bit surprised this has not shown anywhere else
<rburton> armv5 is old school, not a lot of people use it :)
<ptsneves> i do :)
<rburton> you should fix it then :)
<ptsneves> i actually wanted to setup a layer for https://www.acmesystems.it/ arietta
<rburton> a quick grep shows that ffmpeg manually links to atomic in armv5
<ptsneves> yes. that is the way to go. The bug mentions "--as-needed -latomic --no-as-needed" for when latomic is used
<vmeson> a few more similar 'fixes' in meta-oe
ruslan has quit [Quit: Client closed]
<ptsneves> vmeson indeed thanks for the hint. I was going to change the CMakeLists file directly
xenador77 has quit [Remote host closed the connection]
xenador77 has joined #yocto
Guest17 has joined #yocto
Tyaku has quit [Quit: Lost terminal]
rfuentess_ has quit [Remote host closed the connection]
tangofoxtrot has quit [Remote host closed the connection]
<ptsneves> what is the policy for open embedded core recipes' packageconfig? Do we enumerate all options even when dependency recipes are not available in openembedded-core?
tangofoxtrot has joined #yocto
<rburton> *all* options? no. some don't make sense
ruslan has joined #yocto
<rburton> plenty of recipes in core have options that only actually work if other layers are present though
Pinta has quit [Quit: Client closed]
<ptsneves> thanks.
<RP> dl9pf: Looks like meta-agl force pushed some tags? :(
<RP> smurray: ^^^
<dl9pf> RP: yes
frieder has quit [Remote host closed the connection]
<Guest17> ruslan: Yeah, now the core-dump systemd service is running. Thanks a lot!
<Guest17> Do you also know how to set and configure its /usr/lib/sysctl.d/50-coredump.conf already in yocto?
<Guest17> poky/meta/ does not contain such file in its file tree
<RP> dl9pf: I'll adapt our code to handle that, it hadn't expected it :/
<ruslan> Guest17: in running Yocto image or during build?
<Guest17> ruslan: in running Yocto image
<ruslan> So just use editor
<smurray> RP: I’m on vacation until next week, but it looks like dl9pf caught it
<Guest17> ok
<Guest17> thanx!
Guest17 has quit [Quit: Guest17]
ptsneves has quit [Ping timeout: 252 seconds]
ruslan has quit [Quit: Client closed]
pgowda_ has quit [Quit: Connection closed for inactivity]
nemik has quit [Ping timeout: 272 seconds]
<fray> Wondering, has anyone brought up adding a cortex-a78 tune to oe-core yet?
<fray> (I didn't see it when I looked, but also only looked for filenames)
nemik has joined #yocto
seninha has quit [Quit: Leaving]
<rfs613> what criteria determine if a layer is "Yocto Project Compatible"? The list at https://www.yoctoproject.org/software-overview/layers/ seems to include mostly ancient yocto versions
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
armhzjz has quit [Quit: leaving]
amitk has joined #yocto
kscherer_ has joined #yocto
kscherer has quit [Ping timeout: 268 seconds]
<dl9pf> RP we're reducing tag usage - should fix this
creich has joined #yocto
xenador77 has quit [Remote host closed the connection]
xenador77 has joined #yocto
seninha has joined #yocto
mckoan is now known as mckoan|away
xenador77 has quit [Remote host closed the connection]
xenador77 has joined #yocto
creich has quit [Quit: Leaving]
<rburton> fray: harass jonmason :)
<fray> ya, figured I'd ask first
<jonmason> I added everything that existed in GCC at the time, I guess there is a new gcc now
<jonmason> and maybe I can fix spelling mistakes this time :)
<fray> last I looked (gcc 11) a78 was listed, but was the same (effectively) as a72
<fray> I didn't look at 12 yet
seninha has quit [Quit: Leaving]
twnqx has quit [Ping timeout: 255 seconds]
twnqx has joined #yocto
twnqx has quit [Ping timeout: 246 seconds]
twnqx has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
<otavio> khem: RP: we are debugging a linker error in Rust canadian toolchain. When using the SDK to build a Rust app linked ld-loader is wrong. Is this a known iss
<otavio> ue?
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
florian has joined #yocto
peoliye has joined #yocto
amitk has quit [Ping timeout: 268 seconds]
Herrie has quit [Ping timeout: 246 seconds]
Minvera has joined #yocto
florian has quit [Ping timeout: 260 seconds]
Soopaman has joined #yocto
alicef has quit [Quit: install gentoo]
alicef has joined #yocto
Baehrune has joined #yocto
Guest56 has joined #yocto
Guest56 is now known as typecasto
<JPEW> OE Happy Hour in 10 minutes: https://zoom.us/j/99151508871
Tokamak has joined #yocto
mvlad has quit [Remote host closed the connection]
Baehrune has quit [Ping timeout: 255 seconds]
xenador77 has quit [Remote host closed the connection]
xenador77 has joined #yocto
mihai has quit [Quit: Leaving]
Minvera has quit [Remote host closed the connection]
<typecasto> Every few minutes during the build bitbake keeps checking sstate mirror object availability, which takes about a minute each time, is this normal? Why check more than once? I've never seen it actually grab more than 15% from the sstate mirrors (the first time it checks), should it be grabbing more?
<typecasto> I'm trying to follow along with the quick start guide (I'm completely new to this) but it's gonna take at least 24h to build at the pace it's going on my work laptop, so the more I can speed this up by grabbing from the sstate mirrors the better.
peoliye has quit [Quit: Client closed]
Soopaman has quit [Ping timeout: 246 seconds]
alinucs_ has quit [Quit: ZNC 1.7.5 - https://znc.in]
alinucs has joined #yocto
<moto-timo> Anybody have a hint how to quiet this warning?
<moto-timo> WARNING: myimage-pkg-1.0-r0 do_package: Manifest /build/tmp/sstate-control/manifest-x86_64_x86_64-nativesdk-myimage-image.packagedata not found in armv8a_tegra194 armv8a_tegra armv8a-crc armv8a aarch64 allarch x86_64_x86_64-nativesdk (variant '')?
<moto-timo> (We package some images to be installed on target... LUKS encryption hacks)
Soopaman has joined #yocto
<fray> sounds like you have a do_install or do_package step that should be deltask'd
Soopaman has quit [Quit: Leaving.]
peoliye has joined #yocto
<abelloni> ah, I missed the happy hour
<typecasto> what's the happy hour?
nemik has quit [Ping timeout: 246 seconds]
jpuhlman_ has joined #yocto
jpuhlman has quit [Killed (zinc.libera.chat (Nickname regained by services))]
jpuhlman_ is now known as jpuhlman
nemik has joined #yocto
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
tgamblin has joined #yocto
<RP> otavio: not really known, no, but I'm not surprised either :/
kscherer_ has quit [Quit: Konversation terminated!]
<otavio> RP: we fixed few things in our end and will prepare a PR for those; the SDK we'll need some help
peoliye has quit [Quit: Client closed]
<RP> otavio: sounds good, thanks
twnqx has quit [Ping timeout: 255 seconds]
Herrie has joined #yocto
roussinm has quit [Quit: WeeChat 3.0]
typecasto has quit [Quit: Client closed]
sotaoverride is now known as Guest4233
v0n has joined #yocto
sotaoverride has joined #yocto
seninha has joined #yocto
xenador77 has quit [Remote host closed the connection]
xenador77 has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
xenador77 has quit [Ping timeout: 252 seconds]
peoliye has joined #yocto