<mbulut>
RP, fyi about quilt not being in PATH: I retried with master and the behavior is the same. Attempted to file a bug but couldn't proceed as "Self-registration is currently disabled..." therefore couldn't create a bugzilla account. Contacted helpdesk to have them create an account for me...
<RP>
mbulut: thanks! Most of them are US based so it should happen in a few hours
olani has joined #yocto
frgo has quit [Remote host closed the connection]
frgo has joined #yocto
mbulut has quit [Ping timeout: 248 seconds]
olani- has joined #yocto
Saur1 has quit [Ping timeout: 252 seconds]
olani has quit [Ping timeout: 276 seconds]
Saur1 has joined #yocto
mbulut has joined #yocto
Saur_Home16 has quit [Quit: Client closed]
Saur_Home16 has joined #yocto
gspbirel56 has quit [Ping timeout: 248 seconds]
Saur is now known as Saur_
Saur1 is now known as Saur
Saur has quit [Quit: Leaving.]
mbulut has quit [Quit: Leaving]
Saur has joined #yocto
frgo has quit [Remote host closed the connection]
frgo has joined #yocto
GNUmoon has quit [Ping timeout: 260 seconds]
GNUmoon has joined #yocto
vthor has joined #yocto
vthor has quit [Changing host]
vthor has joined #yocto
Ad0 has quit [Ping timeout: 252 seconds]
Daanct12 has quit [Quit: WeeChat 4.4.3]
olani has joined #yocto
Dr_Who has joined #yocto
ehussain has quit [Remote host closed the connection]
|Xagen has quit [Ping timeout: 255 seconds]
cyxae has joined #yocto
florian has quit [Quit: Ex-Chat]
rob_w has quit [Remote host closed the connection]
Saur_Home16 has quit [Quit: Client closed]
Saur_Home16 has joined #yocto
Xagen has joined #yocto
Ad0 has joined #yocto
florian has joined #yocto
SEGFAULT-berlin has joined #yocto
<SEGFAULT-berlin>
Hi I am having a problem building kirkstone. ERROR: bmap-tools-native-3.6+gitAUTOINC+c0673962a8-r0 do_fetch: Fetcher failure: Unable to find revision c0673962a8ec1624b5189dc1d24f33fe4f06785a in branch master even from upstream. After investigating it apears the upstream my build references has been archived.
<SEGFAULT-berlin>
Is there going to be an update to kirkstone to correct this?
<SEGFAULT-berlin>
*in kirkstone
<rburton>
SEGFAULT-berlin: try changing branch=master to branch=main, but current kirkstone bmap-tools recipe uses the non-archived repo github.com/yoctoproject/bmaptool
<gears85>
Alright, I'm pretty new to Yocto / BitBake / OE. I'm trying to only install a package for a specific distro. Is there an easy way to do this? It's pretty easy for machine-specific packages using IMAGE_INSTALL:append:<machine-name>. Could I do the same for the distro? Thanks if anyone knows
<rburton>
gears85: :<distroname>
<SEGFAULT-berlin>
sorry for the noob question but we can't figure out where to change our configured kirkstone verson
<SEGFAULT-berlin>
*version
<gears85>
rburton it's that simple? IMAGE_INSTALL:append:<distro name> ? Thanks! I'll try it out
<rburton>
SEGFAULT-berlin: that's something on you can answer. if you use a git clone then bump the sha. if you use a release then 4.0.22 has the master->main change so should work, even with the old repo url.
<SEGFAULT-berlin>
alright, thanks, I will ask in my team
<Saur_>
gears85: If you run `bitbake-getvar OVERRIDES` you should get all active overrides and how they are defined.
<tgamblin>
RP: looks like pkgconfig is missing from inherit, which was supposed to be in my upgrade... I'll test and send a patch
<SEGFAULT-berlin>
rburton after digging though our build system I can confirm we are pulling our sources from our vendor's BSP
<rburton>
if they're not upgrading them complain to them
<SEGFAULT-berlin>
I don't know if this is the right place to ask but is there a way to decouple our source for recipies from what the BSP provides? maybe as a bbappend
<rburton>
SEGFAULT-berlin: don't use their oe-core, use your own
<rburton>
BSPs shouldn't ship forks of oe-core...
<SEGFAULT-berlin>
that's a layer right? (sorry I am first time debugging this deep)
<rburton>
yeah, the meta layer is oe-core
Saur_Home16 has quit [Quit: Client closed]
Saur_Home16 has joined #yocto
<SEGFAULT-berlin>
@rburton we're running NXP's BSP, I need to confirm if that is actually shipping it's own oe-core. I can't make heads or tails of the manifest file that our build system downloads in the fetch stage
<tgamblin>
but, I don't see this if I build manually... it's just when my CI tool does the build
<gmorell>
good morning, I'm attempting to get an x86-64 build of a usually building as ARM image booting as a VM, I have a wks for the partitions setup and have loaded the bzImage in virt-manager, but it gets stuck on "Booting from Hard Disk", just wanted to know if there was something obvious I was missing
<vmeson>
tgamblin: we need a longer link...
jmd has joined #yocto
<tgamblin>
vmeson: rburton: ah, oops... one moment
<rburton>
tgamblin: ah so that's directory ownership problems. did it used to work?
druppy has joined #yocto
frieder has quit [Remote host closed the connection]
<rburton>
tgamblin: its rpm-specific because rpm is a PITA
mbulut has quit [Ping timeout: 252 seconds]
<tgamblin>
rburton: never tried this build before on the system, but my nightly AUH run has never had issues
<tgamblin>
rburton: where do you see the ownership issue?
<rburton>
tgamblin: when different packages are complaining about conflicts over eg /usr/lib the problem is that different packages are for some reason shipping with different ownership on those files
<rburton>
hang on there was a commit that touched this recently
<rburton>
hm 'bitbake.conf: set FILESYSTEM_PERMS_TABLES using ??=' isn't in master yet but might have impacted your sstate if you did a build with that
<tgamblin>
I don't think it did - that log is from a brand new build on master, no sstate
zpfvo has quit [Remote host closed the connection]
<rburton>
sakoman: you might want to see if 669d0df81f651f7c033c8cb7872cac5bfe670a4f backports to kirkstone etc cleanly
<rburton>
hm
florian has joined #yocto
frgo has joined #yocto
<tgamblin>
rburton: fine enough for me to use deb regardless, I just wanted to do a nightly for genericarm64 :)
<tgamblin>
was more worried that maybe something snuck in upstream
<tgamblin>
yeah, when I went and didn't see any failures there I started assuming that I just did something silly locally
gears85 has quit [Quit: Client closed]
gears43 has joined #yocto
dgriego has quit [Quit: Bye]
<tgamblin>
RP: sent a patch to add pkgconfig in python3-numpy
dgriego has joined #yocto
frgo has quit [Remote host closed the connection]
PhoenixMage has quit [Ping timeout: 244 seconds]
PhoenixMage has joined #yocto
florian has quit [Ping timeout: 260 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 255 seconds]
Abp has quit [Ping timeout: 248 seconds]
Abp has joined #yocto
sotaoverride has quit [Ping timeout: 265 seconds]
jmd has quit [Remote host closed the connection]
druppy has quit [Ping timeout: 246 seconds]
Articulus has quit [Quit: Leaving]
frgo has joined #yocto
frgo has quit [Ping timeout: 276 seconds]
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #yocto
cyxae has quit [Remote host closed the connection]
cyxae has joined #yocto
<gears43>
Thanks to whoever pointed me towards the OVERRIDES earlier, when I was asking about distro-specific package installs. It helped me find the problem eventually
frgo has joined #yocto
druppy has joined #yocto
frgo has quit [Ping timeout: 248 seconds]
davidinux1 has quit [Ping timeout: 245 seconds]
sgw has quit [Ping timeout: 252 seconds]
sgw has joined #yocto
florian has joined #yocto
frgo has joined #yocto
frgo has quit [Ping timeout: 276 seconds]
<vmeson>
gears43: that was Saur_ - yay Saur_ ! ;-) [10:55] <Saur_> gears85: If you run `bitbake-getvar OVERRIDES` you should get all active overrides and how they are defined.
<Saur_>
gears43: You're welcome. :)
jsbronder has quit [Ping timeout: 245 seconds]
Kubu_work has quit [Quit: Leaving.]
jsbronder has joined #yocto
davidinux1 has joined #yocto
goliath has joined #yocto
frgo has joined #yocto
frgo has quit [Ping timeout: 245 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
mbulut has joined #yocto
frgo has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #yocto
<RP>
tgamblin: any idea why it happens in some cases and not others?
Abp has quit [Read error: Connection reset by peer]
Abp has joined #yocto
frgo has quit [Ping timeout: 245 seconds]
rfuentess has quit [Remote host closed the connection]
<tgamblin>
RP: no, unfortunately. I just know that I had encountered a similar error during the early upgrade attempts for numpy, and that inheriting pkgconfig fixed it then
Abp has quit [Read error: Connection reset by peer]
<tgamblin>
RP: and somehow I omitted it when sending this latest uprev
Abp has joined #yocto
<RP>
tgamblin: I think we need to understand why this is failing :/
<tgamblin>
RP: I agree. I haven't been able to reproduce it yet though, and I didn't see it at all during the buildall-qemu I ran for the numpy upgrade (which was without this addition)
<JPEW>
khem: I got the go build working. There was a bug in go-vendor.bbclass for which I will send a patch presently
sgw has quit [Read error: Connection timed out]
<tgamblin>
RP: could it be something to do with glibc already inheriting pkgconfig somewhere when building with that as libc, but musl doesn't do it?
* tgamblin
is throwing darts
<RP>
tgamblin: my guess is host python version
<RP>
JPEW: very cool!
<RP>
tgamblin: if that were the case, you'd be able to reproduce it
<RP>
(glibc vs musl)
<tgamblin>
RP: I'm building on Debian with 3.11.2, looks like that builder (F41) has 3.13.x
<tgamblin>
Has header "Python.h" with dependency python-3.13: YES
Abp has quit [Ping timeout: 245 seconds]
frgo has quit [Ping timeout: 272 seconds]
amitk_ has quit [Ping timeout: 246 seconds]
druppy has joined #yocto
olani- has quit [Ping timeout: 252 seconds]
gears43 has quit [Ping timeout: 256 seconds]
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Abp has joined #yocto
<RP>
tgamblin: I could have sworn it didn't find pkg-config on my local build :/
<tgamblin>
RP: I'm setting up to test on F41 but it'll be a bit
<tgamblin>
probably not going to get started until tomorrow
<RP>
tgamblin: no problem, I appreciate the help!
* RP
is deciding the bitbake server timeouts on f40-vk-4 is broken hardware
ashlin4010 has joined #yocto
cyxae has quit [Quit: cyxae]
<ashlin4010>
I have just started working with yocto, I am coming from buildroot. I have for the last week or so been playing around with build a distro and BSP layer.
<ashlin4010>
I been playing with the meta-raspberrypi BSP layer. I customize it a lot, I am on the fence about how to do it.
<ashlin4010>
1. customize it by added new layers .bbappends etc
<ashlin4010>
2. Make a new BSP in include what can be reused and build new what can't be
<ashlin4010>
3. Do it all from scratch, take what is needed from meta-raspberrypi but don't include it in the layers at all
<RP>
ashlin4010: hard to say without knowing what you're doing but I'd probably start at 2) and see where it went
florian has quit [Ping timeout: 252 seconds]
mbulut has quit [Remote host closed the connection]
<ashlin4010>
Yeah, I have started down that path. The biggest unknown is how SOC_FAMILY = "rpi" and MACHINEOVERRIDES affect things, if they do at all. Perhaps I can level them out while I get the basis needs for the rpi worked out (uboot, dts, paration)
druppy has quit [Ping timeout: 252 seconds]
goliath has quit [Quit: SIGSEGV]
<RP>
ashlin4010: You'd have to see where they're used. I don't know the rpi stuff that well now