LetoThe2nd changed the topic of #yocto to: Welcome to the Yocto Project | Learn more: https://www.yoctoproject.org | Community: https://www.yoctoproject.org/community | IRC logs: http://irc.yoctoproject.org/irc/ | Having difficulty on the list, with someone on the list or on IRC, contact Yocto Project Community Manager Letothe2nd | CoC: https://www.yoctoproject.org/community/code-of-conduct
sanbeam18 has joined #yocto
sanbeam9 has joined #yocto
sanbeam18 has quit [Ping timeout: 248 seconds]
tangofoxtrot has quit [Remote host closed the connection]
tangofoxtrot has joined #yocto
ndeuteron has joined #yocto
<ndeuteron> Hello #yocto. In the past I've used langdale to build SDKs targeting arm64 and amd64 so that I can build stuff for an imx8 as well as for PCs using essentially the same build environment and instructions. Now, with scarthgap, I'm having trouble with all the required meta layers for both machines coexisting. Is this considered a bug? Or is it expected now that I should have separate kas configs for
<ndeuteron> building each SDK?
zenstoic has joined #yocto
jclsn has quit [Ping timeout: 272 seconds]
sanbeam18 has joined #yocto
sanbeam9 has quit [Ping timeout: 260 seconds]
jclsn has joined #yocto
jclsn has quit [Ping timeout: 272 seconds]
starblue has quit [Ping timeout: 268 seconds]
starblue has joined #yocto
sanbeam9 has joined #yocto
sanbeam18 has quit [Ping timeout: 260 seconds]
jclsn has joined #yocto
sanbeam9 has quit [Ping timeout: 248 seconds]
sanbeam has joined #yocto
sanbeam9 has joined #yocto
sanbeam has quit [Ping timeout: 248 seconds]
sanbeam9 has quit [Ping timeout: 260 seconds]
zenstoic has quit [Quit: Connection closed for inactivity]
goliath has joined #yocto
ehussain has joined #yocto
enok has joined #yocto
mjacob has quit [Ping timeout: 265 seconds]
mjacob has joined #yocto
rfuentess has joined #yocto
rob_w has joined #yocto
leon-anavi has joined #yocto
CrazyGecko has joined #yocto
ahussain has joined #yocto
frieder has joined #yocto
ehussain has quit [Ping timeout: 272 seconds]
ahussain is now known as ehussain
ahussain has joined #yocto
ehussain has quit [Ping timeout: 248 seconds]
ahussain is now known as ehussain
enok has quit [Read error: Connection reset by peer]
enok has joined #yocto
enok has quit [Ping timeout: 252 seconds]
mckoan|away is now known as mckoan
frgo_ has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
frgo_ has quit [Ping timeout: 252 seconds]
leon-anavi has quit [Read error: Connection reset by peer]
chep has joined #yocto
BoergeSt has joined #yocto
leon-anavi has joined #yocto
ptsneves has joined #yocto
florian has joined #yocto
ablu has quit [Ping timeout: 252 seconds]
ablu has joined #yocto
rfuentess has quit [Ping timeout: 252 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 248 seconds]
<RP> ndeuteron: what kind of trouble? Hard to say without knowing the details but I'd have thought it should work
olani has joined #yocto
rfuentess has joined #yocto
rfuentess has quit [Remote host closed the connection]
rfuentess has joined #yocto
prabhakalad has joined #yocto
florian has quit [Ping timeout: 252 seconds]
mbulut has joined #yocto
ptsneves has quit [Ping timeout: 276 seconds]
mbulut has quit [Client Quit]
florian has joined #yocto
<ndeuteron> RP: I've got it working with BBMASK:genericx86-64 now, to mask off some bits that were causing problems.
<ndeuteron> Some of it is some inhouse stuff from another team, but meta-imx was causing me some grief too, I thought.
<ndeuteron> I'll try enabling that layer again in a bit and see what falls over.
<RP> ndeuteron: the imx stuff is known to be problematic, we don't control that :(
<ndeuteron> Ah, right. This comes from NXP, doesn't it?
<ndeuteron> I guess my BBMASK is probably the way to go then. It's only 3 lines. Not too bad.
DvorkinDmitry has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
<RP> ndeuteron: it does, yes
enok has joined #yocto
florian_kc has joined #yocto
Kubu_work has joined #yocto
<rburton> RP JPEW: proposal: start migrating pkgdata from the ugly existing files to just being in the json. the existing format is a pita to parse.
enok has quit [Quit: enok]
enok has joined #yocto
enok has quit [Remote host closed the connection]
enok has joined #yocto
enok has quit [Client Quit]
enok has joined #yocto
enok has quit [Client Quit]
enok has joined #yocto
enok has quit [Client Quit]
enok has joined #yocto
<RP> rburton: seems reasonable to me. They predate json support in python
ahussain has joined #yocto
ehussain has quit [Ping timeout: 260 seconds]
ahussain is now known as ehussain
ehussain has quit [Ping timeout: 244 seconds]
Dracos-Carazza has quit [Quit: ZNC 1.9.0 - https://znc.in]
<kanavin> ndeuteron, you can create two different templates with separate bblayers.conf.sample files?
<kanavin> then initialize builds pointing to one or the other
<kanavin> in theory layers shouldn't overstep, but we can't control vendors, and they sometimes butcher yocto
Dracos-Carazza has joined #yocto
enok has quit [Quit: enok]
enok has joined #yocto
Dracos-Carazza has quit [Quit: ZNC 1.9.0 - https://znc.in]
Dracos-Carazza has joined #yocto
enok has quit [Ping timeout: 252 seconds]
enok has joined #yocto
Dracos-Carazza has quit [Quit: ZNC 1.9.0 - https://znc.in]
Dracos-Carazza has joined #yocto
rob_w has quit [Remote host closed the connection]
rob_w has joined #yocto
enok has quit [Ping timeout: 265 seconds]
enok has joined #yocto
enok has quit [Ping timeout: 246 seconds]
leon-anavi has quit [Remote host closed the connection]
rob_w has quit [Ping timeout: 272 seconds]
Guest87 has joined #yocto
rob_w has joined #yocto
kanavin has quit [Remote host closed the connection]
leon-anavi has joined #yocto
Guest87 is now known as ciscokid
ciscokid has left #yocto [#yocto]
kanavin has joined #yocto
rob_w has quit [Remote host closed the connection]
<JPEW> rburton: agreed
Xagen has quit [Read error: Connection reset by peer]
Xagen has joined #yocto
enok has joined #yocto
enok has quit [Read error: Connection reset by peer]
<JPEW> Cool
enok has joined #yocto
jmiehe has joined #yocto
enok71 has joined #yocto
vvn has quit [Quit: WeeChat 4.5.1]
enok has quit [Ping timeout: 272 seconds]
enok71 is now known as enok
jmiehe has quit [Quit: jmiehe]
vvn has joined #yocto
cyxae has joined #yocto
goliath has quit [Quit: SIGSEGV]
nvil has joined #yocto
frgo has joined #yocto
frgo has quit [Ping timeout: 272 seconds]
frgo has joined #yocto
rfuentess has quit [Remote host closed the connection]
cyxae_ has joined #yocto
cyxae has quit [Ping timeout: 268 seconds]
cyxae_ is now known as cyxae
Articulus has quit [Quit: Leaving]
dgriego_ has joined #yocto
dgriego has quit [Ping timeout: 268 seconds]
frgo has quit [Remote host closed the connection]
dgriego_ has quit [Ping timeout: 248 seconds]
frgo has joined #yocto
goliath has joined #yocto
enok71 has joined #yocto
dgriego has joined #yocto
dgriego has quit [Client Quit]
enok has quit [Ping timeout: 265 seconds]
rm5248 has joined #yocto
enok71 has quit [Ping timeout: 268 seconds]
<rm5248> Hi, is anybody aware of a basic yocto image that uses GNOME? I'm trying to get it working, but whenever yocto boots in qemu it's complaining about missing /usr/bin/x-window-manager.
florian_kc has quit [Ping timeout: 265 seconds]
frgo has quit [Remote host closed the connection]
Nrpt has joined #yocto
leon-anavi has quit [Quit: Leaving]
<kanavin> you probably need meta-gnome from meta-openembedded repo. Not sure if it comes with reference image recipes, you should check that
frgo has joined #yocto
Nrpt29 has joined #yocto
mckoan is now known as mckoan|away
Nrpt29 has quit [Client Quit]
pbsds35 has quit [Ping timeout: 268 seconds]
frgo has quit [Remote host closed the connection]
frieder has quit [Remote host closed the connection]
jbo_ has joined #yocto
jbo has quit [Ping timeout: 252 seconds]
amitk_ has joined #yocto
amitk has quit [Ping timeout: 260 seconds]
jbo has joined #yocto
jbo_ has quit [Ping timeout: 245 seconds]
nvil has quit [Quit: Client closed]
florian_kc has joined #yocto
pbsds35 has joined #yocto
Nrpt has quit [Quit: Client closed]
ptsneves has joined #yocto
olani has quit [Ping timeout: 244 seconds]
<khem> there is no reference image but it should be easy to add one, inherit from core-image-base and add packagegroup-gnome-apps and packagegroup-gnome-desktop to IMAGE_INSTALL
<khem> RP:yeah its due to glibc 2.41 headers and clang combo some FORTIFY_SOURCES thing not doing well on x86
<khem> for g-i
<khem> I have submiited a fix for this to meta-clang, should be in today
<khem> btw https://autobuilder.yoctoproject.org/valkyrie/ seems to be down with 502 Bad Gateway
<rm5248> khem: Ah, I didn't see the packagegroup-gnome-apps at all, I'll try that out and see what happens.
rm5248 has quit [Ping timeout: 260 seconds]
<RP> khem: it was 502 as we were in the weekly maintenance window
<rburton> RP: cve update failed, don't merge
<RP> rburton: got it. Please reply on list
<rburton> already have
<RP> rburton: thanks. I'd not looked at email yet
* RP is happy to say we've moved the autobuilder to buildbot 4.x
<RP> thanks mathieudb and halstead
<halstead> khem: RP, I can set up a more useful 502 error page before the next maintenance period.
frgo has joined #yocto
cabazon has joined #yocto
olani has joined #yocto
frgo has quit [Ping timeout: 244 seconds]
rm5248 has joined #yocto
<ebassi> Before I commit to it, are there scripts that turn an image manifest into a structured format, like JSON?
cabazon has quit [Quit: Client closed]
<RP> ebassi: which form of image manifest? SPDX?
<RP> JPEW: did you write that script? :)
<RP> JPEW: I did merge the fixes FWIW
<JPEW> RP: SPDX is missing the file size property; we could add it in a custom annotation though
<JPEW> I added the property to the SPDX spec though, so it will be in SPDX 3.1
<RP> JPEW: right, I think even the list of things would be a good start right now...
<JPEW> Ya, just a list of files then?
<RP> JPEW: or packages, just to show how you can process the SPDX easily
<JPEW> Ya, I have that
florian has quit [Killed (NickServ (GHOST command used by florian_kc!~florian@dynamic-078-048-091-158.78.48.pool.telefonica.de))]
florian_kc is now known as florian
florian_kc has joined #yocto
<JPEW> I can send it it as a contrib script
<RP> JPEW: that would be cool thanks!
<RP> JPEW: I just want to show this isn't hard
<JPEW> Yep
ptsneves has quit [Ping timeout: 252 seconds]
<ebassi> RP: the `component arch version` manifest
<RP> ebassi: I need a hint. pkgdata? something in the package manager? sstate? SPDX? something in deploy?
<RP> we have far too many manifests :/
sanbeam9 has joined #yocto
goliath has quit [Quit: SIGSEGV]
cyxae has quit [Quit: cyxae]
<ebassi> RP: Yeah, I noticed :-)
Kubu_work has quit [Quit: Leaving.]
<RP> ebassi: I think if it were me, I'd take the SPDX and process what you need from that. Those files don't look very machine readable. I'd take patches rewriting them in json too
<RP> ebassi: code is in meta/classes-recipe/rootfs-postcommands.bbclass in write_image_manifest() and I'm torn between deleting it and telling people to use SPDX or rewriting that to json. You can easily add your own post commands like that too FWIW
<RP> ebassi: I give it 50/50 odds the code survives past midday tomorrow if rburton reads this in the morning :)
<RP> alternatively I might get annoyed enough with javascript and react to want to do that as therapy
sanbeam18 has joined #yocto
<ebassi> hehe
sanbeam9 has quit [Ping timeout: 276 seconds]
florian has quit [Ping timeout: 252 seconds]
sanbeam18 has quit [Ping timeout: 260 seconds]