<moto-timo>
you probably want SRC_URI:append:rock-pi-3a (paraphrasing off the top of my head)
<moto-timo>
In regular language that means "append the SRC_URI variable if the machine override 'rock-pi-3a' is present"
<PhoenixMage>
moto-timo: I want to overwrite as I need to switch from mainline u-boot to the rockchip fork because the SBC isnt in mainline yet
sakoman has quit [Quit: Leaving.]
<moto-timo>
Probably ask tlwoerner for rockchip specific stuff
<PhoenixMage>
thanks moto-timo. tlwoerner let me know when you are free for a chat :)
davidinux has quit [Ping timeout: 246 seconds]
davidinux has joined #yocto
vmeson has quit [Ping timeout: 252 seconds]
vmeson has joined #yocto
amitk has joined #yocto
<tlwoerner>
PhoenixMage: the meta-rockchip on git.yoctoproject.org is for running upstream, mainline code on a rockchip
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
<tlwoerner>
PhoenixMage: if you're interested in running all the vendor forks and closed things then i recommend trying https://github.com/JeffyCN/meta-rockchip
<PhoenixMage>
tlwoerner: I would prefer not to run vendor forks, but kinda stuck with rock-3a as no mainline yet
<PhoenixMage>
I will check out that fork though
<tlwoerner>
PhoenixMage: yes, i have the rock-3a too, and my rock5 model B showed up the other day (haven't had a chance to play with either yet)
<tlwoerner>
but rockchip is fairly good (all things considered) at getting upstream support eventually so... fingers crossed :-)
<PhoenixMage>
tlwoerner: I literally just paid for my Rock 5b about 15 min ago, hoping to have it in the week
<tlwoerner>
nice!
<PhoenixMage>
I think there is mainline kernel support for the rk3568 isnt there?
nemik has quit [Ping timeout: 272 seconds]
<PhoenixMage>
Seems a lot of the mainline push comes from the armbian ppl
nemik has joined #yocto
<tlwoerner>
PhoenixMage: huh, looks like there is. i thought i checked recently. looks like the kernel has support, but not U-Boot
<PhoenixMage>
tlwoerner: Yeah thats why I started messing with meta-rockchip, keep the mainline kernel but override u-boot to use the vendor one until mainline is done. Will make it easier to just switch it to mainline u-boot when available
<tlwoerner>
PhoenixMage: sounds good
<tlwoerner>
PhoenixMage: is your plan to use rkdeveloptool to load the vendor U-Boot spi flash?
<PhoenixMage>
One thing at a time lol
<PhoenixMage>
I havent got a plan :p I am fairly new to all this embedded stuff
<PhoenixMage>
And I dont use SPI on my 4b's either
sakoman has joined #yocto
starblue has quit [Ping timeout: 248 seconds]
starblue has joined #yocto
schtobia has quit [Quit: Bye!]
schtobia has joined #yocto
jclsn has quit [Ping timeout: 246 seconds]
jclsn has joined #yocto
amitk has quit [Ping timeout: 252 seconds]
amitk has joined #yocto
sakoman has quit [Ping timeout: 252 seconds]
sakoman has joined #yocto
sakoman has quit [Quit: Leaving.]
xmn has quit [Ping timeout: 255 seconds]
alessioigor has joined #yocto
schtobia has quit [Quit: Bye!]
<PhoenixMage>
I am confused, the radxa u-boot is using an old Makefile, the target u-boot-initial-env which is used by the mainline build is missing, thats fine I patch it in because it is just a call to an existing target "u-boot.bin". Patched in, can see the new target but the new target cant see the old one when I run yocto, if I do it manually its fine...
fray has quit [Read error: Software caused connection abort]
fray has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
amitk has quit [Ping timeout: 252 seconds]
amitk has joined #yocto
nemik has joined #yocto
marka has quit [Ping timeout: 250 seconds]
marka has joined #yocto
ykrons has quit [Ping timeout: 250 seconds]
ykrons has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alicef has quit [Read error: Software caused connection abort]
alicef has joined #yocto
schtobia has joined #yocto
rob_w has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
Vonter has quit [Ping timeout: 272 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
Vonter has joined #yocto
frieder has joined #yocto
mckoan|away is now known as mckoan
<mckoan>
good morning
zpfvo has joined #yocto
Vonter has quit [Ping timeout: 255 seconds]
Vonter has joined #yocto
Payam has joined #yocto
<LetoThe2nd>
yo dudX
davidinux has quit [Ping timeout: 255 seconds]
vquicksilver has quit [Ping timeout: 248 seconds]
davidinux has joined #yocto
* alessioigor
waves all
denisoft81 has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
zwhale has joined #yocto
vquicksilver has joined #yocto
leon-anavi has joined #yocto
ykrons has quit [Ping timeout: 252 seconds]
ykrons has joined #yocto
Schlumpf has joined #yocto
alessioigor has quit [Ping timeout: 252 seconds]
denisoft81 has quit [Quit: Leaving]
<zwhale>
how can we enable/disable trace features such as ftrace in my yocto build? And is it enabled or disabled by default?
zpfvo has quit [Quit: Leaving.]
zwhale has quit [Quit: Client closed]
denisoft81 has joined #yocto
zpfvo has joined #yocto
<qschulz>
o/
GNUmoon has quit [Ping timeout: 258 seconds]
GNUmoon has joined #yocto
Vonter has quit [Ping timeout: 252 seconds]
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
fray has quit [Ping timeout: 255 seconds]
mvlad has joined #yocto
denisoft81 has quit [Remote host closed the connection]
camus has quit [Ping timeout: 248 seconds]
camus1 has joined #yocto
denisoft81 has joined #yocto
camus has joined #yocto
alessioigor has joined #yocto
camus1 has quit [Ping timeout: 248 seconds]
zwhale has joined #yocto
<zwhale>
qschulz I don't know what o/ means :)
<zwhale>
apparently I've asked a dumb question haha
<qschulz>
zwhale: the o is the head, the / is the arm, it's basically waving at someone
fray has joined #yocto
<qschulz>
could be used in different contexts, but it's a way to say "hi" or also "me" (like raising your hand when someone asks "who does/thinks <smth>"
<zwhale>
qschulz ah cool, I got to learn these things one day :)
<zwhale>
getting too old to keep up with these things
manuel1985 has joined #yocto
<qschulz>
I think it's pretty old IRC "slang"? at least it's not new I think
<RP>
qschulz: I just thought you must have a cat :)
GNUmoon has quit [Ping timeout: 258 seconds]
GNUmoon has joined #yocto
<qschulz>
RP: and now I'm wondering how you came up with this thought? What's the context?
<landgraf>
(^_^)/
<RP>
qschulz: random characters from people have often been their cat wandering over the keyboard
<qschulz>
RP: as far as I know, the hair on my shirt aren't visible over IRC. Am I spied on? Is the cover on the webcam on
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<qschulz>
RP: hehe, she just rests on my arm so it makes it difficult to move the mouse or type with two hands. Sometimes she scratches her head against the ctrl key (edge of the keyboard) or play with the noisy space bar
<qschulz>
but she has never sent anything yet
<qschulz>
(I also don't work enough from home for this to happen)
<RP>
qschulz: I think the're all different, I do have a friend who had to get a second keyboard for the cat to lie on so they could work though! :)
denisoft81 has quit [Remote host closed the connection]
<RP>
kanavin: quite surprised at the price of that as a piece of perspex! :)
<qschulz>
RP: "difficult" to make yourself and you only need it once, it's not going to be obsolete or a better version out next year :)
<qschulz>
RP: and if your cat is picky and needs the same keyboard to be fooled, it can get expensive quite fast :D
Vonter has joined #yocto
<RP>
qschulz: not hard to do if you have a heat gun. I suspect my definition of difficult is a bit odd though!
prabhakarlad has quit [*.net *.split]
Payam has quit [*.net *.split]
Schlumpf has quit [*.net *.split]
zwhale has quit [*.net *.split]
GNUmoon has quit [*.net *.split]
florian_kc has joined #yocto
Vonter has quit [Ping timeout: 252 seconds]
<qschulz>
RP: some people find screwing difficult :)
Vonter has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
kanavin has quit [Read error: Connection reset by peer]
kanavin_ has joined #yocto
davidinux has quit [Ping timeout: 252 seconds]
davidinux has joined #yocto
leonanavi has joined #yocto
vquicksilver has quit [Ping timeout: 252 seconds]
vquicksilver has joined #yocto
leon-anavi has quit [Ping timeout: 252 seconds]
sappy has joined #yocto
mckoan is now known as mckoan|away
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
sappy has quit [Quit: Quit]
sappy has joined #yocto
seninha has joined #yocto
fray has quit [Ping timeout: 252 seconds]
fray has joined #yocto
sappy has quit [Quit: Quit]
<rburton>
is Vyacheslav Yurkov on irc?
xantoz has quit [Read error: Connection reset by peer]
zpfvo has quit [Ping timeout: 272 seconds]
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
florian_kc has quit [Ping timeout: 252 seconds]
florian_kc has joined #yocto
zpfvo has joined #yocto
denisoft81 has quit [Quit: Leaving]
amelius 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
<JaMa>
I assume rust changes built fine on autobuilder, but is anyone else seeing "error[E0405]: cannot find trait `FnOnce` in this scope" build failures with today's oe-core? seeing it in python3-bcrypt python3-cryptography and some other recipes
alessioigor has quit [Quit: alessioigor]
davidinux has quit [Ping timeout: 248 seconds]
alessioigor has joined #yocto
kscherer has joined #yocto
davidinux has joined #yocto
sakoman has joined #yocto
xmn has joined #yocto
sa7mfo has quit [Ping timeout: 272 seconds]
zpfvo has quit [Ping timeout: 252 seconds]
prabhakarlad has joined #yocto
rob_w has quit [Remote host closed the connection]
zpfvo has joined #yocto
<tlwoerner>
RP: pair programming... with a cat (lol)
jjmcdn has joined #yocto
Guest13 has joined #yocto
<Guest13>
Hi, what could be the reason why the syslog file is created too late? Almost 2 minutes after the operating system is booted, syslog file is created in /var/log.
Schlumpf has joined #yocto
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 248 seconds]
gchamp has joined #yocto
nemik has joined #yocto
Guest1338 has joined #yocto
Guest13 has quit [Ping timeout: 260 seconds]
prabhakarlad has quit [Ping timeout: 260 seconds]
Schlumpf has quit [Ping timeout: 260 seconds]
Schlumpf has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
zpfvo has quit [Ping timeout: 246 seconds]
prabhakarlad has joined #yocto
zpfvo has joined #yocto
sa7mfo has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
prabhakarlad has quit [Ping timeout: 260 seconds]
prabhakarlad has joined #yocto
Schlumpf has quit [Ping timeout: 260 seconds]
Guest1338 has quit [Quit: Client closed]
seninha has quit [Ping timeout: 246 seconds]
Payam has joined #yocto
Ram-Z has quit [Read error: Software caused connection abort]
<Payam>
Hi I am not so experience in Yocto. but my team have two repositories. One for the yocto build itself with the layers and one for the apps and so on.
<Payam>
so everytime they add an app they build the whole yocto project
<Payam>
this is a yocto based agl.
<Payam>
I though that people first build AgL and then add the apps like in any linux distro
<Payam>
am I wrong?
<LetoThe2nd>
Payam: yes and no. yes, you always build the full system, not just the apps. no, you don't always start from scratch but use a sstate
<Payam>
ys I know.
<Payam>
but idid not know that you build the whole system
Ram-Z has joined #yocto
<LetoThe2nd>
Payam: there are variations, like using package management on the device and such, but in general, you build images.
<Payam>
hmm that is interesting.
<LetoThe2nd>
like i said, you can look into package management or other techniques. but it really depends on your use case/workflow then.
zpfvo has quit [Ping timeout: 252 seconds]
Vonter has quit [Ping timeout: 272 seconds]
PhoenixMage has quit [Ping timeout: 248 seconds]
manuel1985 has quit [Ping timeout: 272 seconds]
Vonter has joined #yocto
PhoenixMage has joined #yocto
zpfvo has joined #yocto
amelius_ has joined #yocto
sakoman has quit [Ping timeout: 252 seconds]
xmn has quit [Ping timeout: 252 seconds]
florian_kc has quit [Ping timeout: 252 seconds]
amelius has quit [Ping timeout: 252 seconds]
florian_kc has joined #yocto
sakoman has joined #yocto
xmn has joined #yocto
yann has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
alessioigor has quit [Quit: alessioigor]
florian_kc has quit [Ping timeout: 255 seconds]
zpfvo has quit [Ping timeout: 246 seconds]
florian has quit [Quit: Ex-Chat]
Vonter has quit [Ping timeout: 248 seconds]
Vonter has joined #yocto
nemik has quit [Ping timeout: 248 seconds]
Payam has quit [Quit: Client closed]
zpfvo has joined #yocto
nemik has joined #yocto
sa7mfo has quit [Ping timeout: 252 seconds]
sa7mfo has joined #yocto
prabhakarlad has quit [Quit: Client closed]
<RP>
JaMa: autobuilder seemed ok :/
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
zpfvo has quit [Quit: Leaving.]
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
prabhakarlad has joined #yocto
<tlwoerner>
RP: one of the questions that i kept asking yesterday regarding the dummy package for the sdk was why were bash and perl being installed despite the existance of the dummy package
<tlwoerner>
but i think i see where i went wrong
<tlwoerner>
RP: the dummy package is to prevent those tools from being installed into the *target* sysroot (?)
<RP>
tlwoerner: it depends on the package
<tlwoerner>
i kept looking in the host-native sysroot and they were always there then was scratching my head as to why
<RP>
tlwoerner: we have host and target ones
<tlwoerner>
dummies?
<tlwoerner>
host-dummy and target-dummy?
<tlwoerner>
i thought it was a noarch dummy
<RP>
meta/recipes-core/meta/target-sdk-provides-dummy.bb vs meta/recipes-core/meta/nativesdk-buildtools-perl-dummy.bb
<tlwoerner>
not to mention meta/recipes-core/meta/nativesdk-sdk-provides-dummy.bb
<tlwoerner>
a "fix" that i came up with is to remove the RCONFLICTS line from meta/recipes-core/meta/dummy-sdk-package.inc
<tlwoerner>
do dummy packages and "real" packages need to conflict?
<tlwoerner>
if the user explicitly asks for perl to be installed, the underlying package system will happily install one then say it's already installed the second time
<RP>
tlwoerner: if you want perl, you probably need a dummy recipe which doesn't provide it
frieder has quit [Remote host closed the connection]
<mischief>
i'd think it would be PACKAGECONFIG = "", but PACKAGECONFIG_CONFARGS is still populated with the PACKAGECONFIG conf arguments by base.bbclass
<rburton>
depends where you're setting PACKAGECONFIG
<mischief>
in a bbappend
<rburton>
then your bbappend isn't being applied
<rburton>
"bitbake-getvar -r perl PACKAGECONFIG" will prove that
<mischief>
it is though, i see it set to "" in bitbake -e
<mischief>
gdbm is blacklisted because it is gpl 3.
<rburton>
oh fun, perl changed again
<rburton>
i don't think we have an explicit test for this
<rburton>
what yocto release?
<mischief>
kirkstone
<mischief>
we set INCOMPATIBLE_LICENSE to remove GPL-3.0 which gdbm appears to be
<mischief>
(and use meta-gplv2, for better or worse)
<rburton>
might be worth trying "bitbake perl -C unpack" to verify that this isn't perl being terrible at rebuilds, as kirkstone might not have the always-build-from-clean commit
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
<mischief>
it seems to me that the issue might be base.bbclass setting PACKAGECONFIG_CONFARGS to -Ui_db -Ui_gdbm even though PACKAGECONFIG was cleared. why is that?
<rburton>
those are the 'disable' values
amitk has quit [Ping timeout: 248 seconds]
<mischief>
oh, duh.
<mischief>
is there a way to avoid perl being built for the target at all? we don't actually have it in our rootfs..
<rburton>
you *could* figure out why its being pulled into the dependency tree and disable it. setting INCOMPATIBLE_LICENSE in the image recipe instead of globally is a better way to do it, fwiw.
<rburton>
typically you don't care if you build perl locally with gpl3 bits, you care if they get shipped.
nemik has quit [Ping timeout: 252 seconds]
<rburton>
the dependency could be via a test case in a ptest recipe that you're not installing
nemik has joined #yocto
<mischief>
that does seem like a good approach, it is sometimes handy to have eg gdb in developer builds and not production builds
<rburton>
right
<rburton>
just move the assignment to the image recipe that you care doesn't have any gpl3 code in
<mischief>
ah, i did disable ptest recently, but that was only on the main branch and not my kirkstone integration branch :(
<mischief>
i guess i need to rebase again
<rburton>
reminder that you should *always* make your own distro if you're using yocto in production, don't use poky and fiddle it. make your own distro with your own DISTRO_FEATURES. if you don't want ptest then you can not enable it in the first place. ditto stuff like vulkan.
<mischief>
weird, do_package_qa passed for perl this time.
olani has joined #yocto
olani- has joined #yocto
<JaMa>
RP: one of my builds was also a bit more successful, except buildpaths QA check, will investigate
<JaMa>
WARNING: python3-bcrypt-4.0.0-r0 do_package_qa: QA Issue: File /usr/lib/python3.11/site-packages/bcrypt/_bcrypt.abi3.so in package python3-bcrypt contains reference to TMPDIR [buildpaths]
<JaMa>
WARNING: python3-cryptography-38.0.1-r0 do_package_qa: QA Issue: File /usr/lib/python3.11/site-packages/cryptography/hazmat/bindings/_rust.abi3.so in package python3-cryptography contains reference to TMPDIR [buildpaths]
<vvn>
hi there -- how does bitbake deal with concurrent builds on the same machine? i.e. multiple devs building images
<JPEW>
vvn: They need to use separate TMPDIR
<JPEW>
vvn: probably even separate build dirs
<vvn>
I'm ok with that, but I
<vvn>
but I'm wondering what happens in terms of core usage
<vvn>
i.e. if 2 people build an imagine including, let's say, qtwebengine :)
<JPEW>
You might look at the new PSI support that was added, but otherwise they just both run oblivious to each other
<vvn>
I'm asking because I think bitbake checks the number of core when it starts, so by default it'll use all of them (or N-1 core). Then if a second user starts a bitbake instance, not sure what happens
<JPEW>
It's just asking the hardware, it's not checking how many cores are "used" or not
<JPEW>
e.g. the current CPU load doesn't affect that query
seninha has quit [Quit: Leaving]
mark_ has joined #yocto
mark_ is now known as mk41
Estrella__ has quit [Remote host closed the connection]
Estrella__ has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
<LetoThe2nd>
rburton: turns out $coworker had this: addtask mymagic after do_install before do_populate_sysroot
<LetoThe2nd>
seems to cause the problem, had him change it to a do_install:append and is supposedly fine now.
florian_kc has joined #yocto
florian_kc has quit [Ping timeout: 252 seconds]
Vonter has quit [Ping timeout: 252 seconds]
leonanavi has quit [Quit: Leaving]
Vonter has joined #yocto
mvlad has quit [Remote host closed the connection]
florian_kc has joined #yocto
olani- has quit [Ping timeout: 246 seconds]
olani has quit [Ping timeout: 246 seconds]
olani has joined #yocto
olani- has joined #yocto
_whitelogger has joined #yocto
<khem>
LetoThe2nd: is it regarding the tar issue ?
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
<RP>
JaMa: I've not see those :/
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
<JaMa>
RP: I see them only with qemuarm64, but not with qemux86-64