michalkotyla has quit [Read error: Connection reset by peer]
mckoan|away is now known as mckoan
<mckoan>
good morning
ThomasRoos has quit [Remote host closed the connection]
rob_w has joined #yocto
michalkotyla has joined #yocto
mvlad has joined #yocto
qschulz has quit [Read error: Connection reset by peer]
qschulz has joined #yocto
vladest has quit [Remote host closed the connection]
vladest has joined #yocto
ptsneves has joined #yocto
nate02 has quit [Remote host closed the connection]
nate02 has joined #yocto
goliath has joined #yocto
nate02 has quit [Ping timeout: 240 seconds]
rfuentess has joined #yocto
kroon has quit [Quit: Leaving]
tnovotny has joined #yocto
josenieto has quit [Quit: Client closed]
manuel1985 has joined #yocto
kroon has joined #yocto
tre has joined #yocto
<LetoThe2nd>
yo dudX
F_Adrian has quit [Quit: Leaving]
bps has joined #yocto
bps has joined #yocto
ilunev has joined #yocto
<mckoan>
hey LetoThe2nd
florian has joined #yocto
<LetoThe2nd>
yo mckoan
<qschulz>
greetings
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
Schlumpf has joined #yocto
yocton_ is now known as yocton
<JaMa>
Did someone measure perf impact of using XZ_DEFAULTS/ZSTD_THREADS in bitbake's fetcher unpack? unpacking 1.4G chromium-101*.tar.xz was shown in htop for quite long time
<JaMa>
rustc (54M+130M), gcc (79M), linux (118M), qemu (120M), firefox (303M) are other 5 biggest *.xz in my small downloads dir (no *zst)
<RP>
JaMa: I've never looked FWIW
<JaMa>
if the benchmark looks promissing, would it make sense to use the same variables and defaults we have in bitbake.conf?
<JaMa>
well except the oe.utils.cpu_count :/
nathani has joined #yocto
alessioigor has joined #yocto
alessioigor has quit [Client Quit]
otavio has quit [Remote host closed the connection]
deuteron_ has joined #yocto
deuteron_ has quit [Client Quit]
<qschulz>
what are the chances my bluetooth headset completely stopped working the day before a talk...
leon-anavi has joined #yocto
kroon has quit [Ping timeout: 260 seconds]
<RP>
JaMa: probably
<LetoThe2nd>
qschulz: 100.1% (rough estimate)
dtometzki has quit [Ping timeout: 272 seconds]
starblue has quit [Ping timeout: 240 seconds]
kroon has joined #yocto
<qschulz>
LetoThe2nd: screen sharing does not work either. I love Zoom.
starblue has joined #yocto
olani has quit [Ping timeout: 260 seconds]
olani has joined #yocto
pgowda_ has joined #yocto
<LetoThe2nd>
qschulz: for massively varying definitions of "love", i presume.
seninha has joined #yocto
jmiehe has quit [Quit: jmiehe]
argonautx has joined #yocto
<qschulz>
LetoThe2nd: thoughts probably incompatible with the CoC unfortunately
LAZIBI has joined #yocto
<LetoThe2nd>
qschulz: +1
nathani has quit [Ping timeout: 260 seconds]
dgriego has joined #yocto
kroon has quit [Quit: Leaving]
LAZIBI has quit [Quit: Client closed]
dgriego has quit [Client Quit]
dgriego has joined #yocto
dgriego has quit [Client Quit]
<jclsn[m]>
LetoThe2nd: Long time no write
<jclsn[m]>
Guys, how is it possible that a recipe builds fine with Bitbake and compiling it with the toolchain throws me errors? Shouldn't they be identical?
<qschulz>
jclsn[m]: compiler flags?
<jclsn[m]>
qschulz: Those should be defined in the CMake toolchain config, shouldn't they?
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
argonautx_ has joined #yocto
argonautx has quit [Read error: Connection reset by peer]
wmills has quit [Read error: Connection reset by peer]
wmills has joined #yocto
<qschulz>
@all: Just a reminder that we're about to start Day 1 of the Yocto Project Summit 2022.05.
simonew has joined #yocto
Baehrune has joined #yocto
ektor5 has joined #yocto
<rburton>
jclsn[m]: should, yes. should isn't definitely :)
<rburton>
could be dependencies though, are you sure you have all the build deps present
<jclsn[m]>
<qschulz> "@all: Just a reminder that we're..." <- Online?
<ptsneves>
LAZIBI it is not easy to understand what is your problem from the post
florian_kc has joined #yocto
<LAZIBI>
ptsneves: Am trying to integrate rauc(systemAB update solution ) to my yocto project, I succeed to build an image, contains rauc inside, but it is nor working properly. As I understood my issue is related to fw_*, any idea how tests that the fw_* tools woks correctly ?
kscherer has joined #yocto
m_jimmer12345 has joined #yocto
<m_jimmer12345>
This lady is the BEST !
<shoragan[m]>
LAZIBI: with fw_* i meant the u-boot environment tools fw_printenv and fw_setenv
<Guest87>
how would i go about requesting for commit 0bd00122643aacd4a0156979436da909cc483b2e (rust: update 1.59.0 -> 1.60.0) to be cherrypicked to the kirkstone branch of openembedded ?
<LAZIBI>
shoragan: yes!
<LAZIBI>
shoragan[m]: yes!
<shoragan>
LAZIBI, it looks like fw_printenv hangs on flock on /var/lock/fw_printenv.lock. the usual cause is that another process that already got that lock first
<ptsneves>
LAZIBI have you added the files to a slot? Assuming you want this files as raw binaries in the disk image
<shoragan>
lsof or fuser might help to find that other process
<shoragan>
LAZIBI, you fw_env.config looks very strage, too. mmmblk devices don't have erase sizes (the third parameter)
<shoragan>
and you probably don't want to place it 15MiB into a 15MiB partition
<shoragan>
or 15MiB into your linux partition
<LAZIBI>
ptsneves: I did not got what u meant !
<ptsneves>
LAZIBI you are using meta-rauc correct?
florian_kc has quit [Ping timeout: 260 seconds]
<LAZIBI>
shoragan: okay will see with lsof or fuser what I find, otherwise even without the 3rd parameter I had the same issue(with just the dev offset and the env. size)
<LAZIBI>
ptsneves yes, I followed the documentation and the meta-rauc-community examples.
florian has quit [Quit: Ex-Chat]
<shoragan[m]>
ptsneves: i think so, but according to the strace in https://github.com/rauc/rauc/issues/908 it looks like rauc executes fw_printenv correctly. it just hangs on the flock as in the stackoverflow question. waiting for flock at that point has nothing to do with rauc ;)
<ptsneves>
ok so i am out of depth. Sorry for the confusion LAZIBI and shoragan[m].
<LAZIBI>
no problem ptsneves, thanks anyway
<qschulz>
Guest87: I'm not sure this will be possible, we usually don't take upgrades. I don't know if we say 1.59.0 -> 1.60.0 is a minor upgrade. What you can do is send a patch to the mailing list specifically for kirkstone and see what people say :)
<qschulz>
ooorrr... ask sakoman very nicely and he might answer what's the policy for stable releases :)
<sakoman>
Guest87: if the version update is a security/bug fix release with no new features or behavior/api changes then it will be considered
<jaskij[m]>
qschulz: what about an upgrade (or a downgrade) in the face of a massive performance regression?
<rburton>
jaskij[m]: in the protobuf case sending an upgrade might be the best thing to do
sashko has quit [Ping timeout: 240 seconds]
<jaskij[m]>
rburton: that's probably the hardest solution, sadly. At least one of the patches failed to apply. I'll try to look in my free time, at work I sadly don't have the time for that.
argonautx_ has quit [Quit: Leaving]
<kanavin_>
Guest87, the correct solution is making a mixin layer
tre has quit [Remote host closed the connection]
<kanavin_>
google for meta-lts-mixins
<kanavin_>
the updated directly in kirkstone will almost certainly be rejected, rust releases are never bugfix only
<Guest87>
kanavin_: that makes sense I am desiring rust 1.60 for some required features in a project i am working on
<kanavin_>
Guest87, then that's your chance to make a community contribution that you can put on your CV
<kanavin_>
a mixin layer for rust updates
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
ektor5 has quit [Quit: WeeChat 3.5]
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
pgowda_ has quit [Quit: Connection closed for inactivity]
Schlumpf has quit [Quit: Client closed]
florian_kc has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
nate02 has joined #yocto
nathani has quit [Ping timeout: 276 seconds]
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
ccf has joined #yocto
<ccf>
Hi, which recipe brings "nice" command into final image?
<neverpanic>
Either coreutils or busybox, depends on which one you have.
<kanavin_>
ccf, 'man nice' reveals that it's a part of coreutils
Tokamak has joined #yocto
tnovotny has quit [Quit: Leaving]
<ccf>
Thanks, it's busybox - but how do I enabled renice and nice there? I guess I need to do a fragment.cfg and add it in my layer. Is there a simple example somewhere?
<ccf>
Or do I need these "bitbake -c menuconfig busybox" and diffconfig stuff?
<qschulz>
that's how you would create a confi fragment I think yes
<michaelo>
Hey, I'm supposed to speak at the YP summit in 20 minutes but I haven't received the connection details (Zoom URL, etc). Could someone share the URL with me in a private message, so that I can at least present my talk?
qschulz has quit [Read error: Connection reset by peer]
<moto-timo>
michaelo: I assume you are busy with two conferences, but did you get a chance to look at my kernel-lab yocto-docs RFC?
* moto-timo
should have waited until after your slot
rfuentess has quit [Remote host closed the connection]
<michaelo>
moto-timo: not yet, will do it tomorrow morning :)
<moto-timo>
michaelo: not urgent, but neither of us should forget to follow up
<michaelo>
Sure!
frieder has quit [Remote host closed the connection]
florian__ has joined #yocto
ljh has joined #yocto
florian_kc has quit [Ping timeout: 276 seconds]
<nate02>
kroon, after much debugging we finally narrowed it down to a change that was made in our distro HOSTTOOLS_NONFATAL = "cvs". Should have been append... Just FYI
qschulz has joined #yocto
seninha has quit [Quit: Leaving]
<Guest87>
what is the expected behavior when multiple layers define SRC_URI[somepackage.sha256sum] ?
<kanavin_>
Guest87, that would be a configuration mistake, layers are not supposed to redefine that
<Guest87>
kanavin_: the rust recipes define SRC_URI[rust.sha256sum] and i need to override it
dgriego_ has quit [Read error: Connection reset by peer]
dgriego has joined #yocto
tarcisb has joined #yocto
sakoman has quit [Quit: Leaving.]
dgriego has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
seninha has joined #yocto
dgriego has joined #yocto
dgriego has quit [Read error: Connection reset by peer]
dgriego has joined #yocto
ljh has quit [Ping timeout: 276 seconds]
<kanavin_>
Guest87, looking
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
<kanavin_>
Guest87, which recipe do I need to build to see the issue?
tarcisb has quit [Quit: Client closed]
<Guest87>
kanavin_: cargo-native does it
<kanavin_>
Guest87, cargo recipes refer to includes from a different directory, and when it happens, bitbake is looking at layers priority. If oe-core has higher priority, they'll come from oe-core.
<kanavin_>
so, tweak priority, or rename your dirs to be 1.60 specific
nemik has quit [Ping timeout: 240 seconds]
<kanavin_>
like recipes-devtools-mixin/ or similar
nemik has joined #yocto
dgriego has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
florian__ has quit [Ping timeout: 276 seconds]
kevinrowland has quit [Ping timeout: 244 seconds]
dgriego has joined #yocto
ptsneves has quit [Ping timeout: 252 seconds]
kevinrowland has joined #yocto
alejandrohs has quit [Ping timeout: 260 seconds]
florian__ has joined #yocto
dgriego has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
kevinrowland has quit [Read error: Connection reset by peer]
dgriego has joined #yocto
kevinrowland has joined #yocto
<Guest87>
kanavin_: I set my layer priorty to 99 and changed the folder name to recipes-devtools-mixin, no change
<kanavin_>
Guest87, you need to fix the path in cargo 1.60 recipes too
<kanavin_>
inside the actual recipe
<kanavin_>
grep recipes-devtools inside your layer
<Guest87>
kanavin_: that looks to have solved it, thanks for your help
<kanavin_>
Guest87, cheers, do you understand why it wasn't working?
<kanavin_>
when you include with a path, bitbake looks the file up in other layers in order of priority.
<kanavin_>
so because the paths were the same between your layer and core, core took precendence.
<Guest87>
kanavin_: that makes sense
<kergoth>
just remember that 'include' 'require' and 'inherit' will obey your BBLAYERS order, not bbfile priority
<Guest87>
kergoth: that explains why changing BBFILE_PRIORITY in my layer had no effect
LAZIBI has quit [Quit: Client closed]
<Saur[m]>
Guest87: You want the layers in `BBLAYERS` to be ordered from highest to lowest priority, i.e., `meta` should typically be the last layer in the list.
kroon has joined #yocto
mvlad has quit [Remote host closed the connection]
dgriego has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dgriego has joined #yocto
dgriego has quit [Read error: Connection reset by peer]
dgriego_ has joined #yocto
m_jimmer12345 has quit [Quit: Client closed]
IanD has quit [Quit: Client closed]
kroon has quit [Quit: Leaving]
Baehrune has quit [Ping timeout: 260 seconds]
dgriego_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
rhowell has joined #yocto
dev1990 has quit [Quit: Konversation terminated!]
dgriego has joined #yocto
<rhowell>
Has anyone had success building u-boot ad-hoc configs on hardknott on a Ubuntu 20.04.4 host? My 20.04.3 machines build it just fine, but my one 20.04.4 machine always has an error "You must add new CONFIG options using Kconfig. The following new ad-hoc CONFIG options were detected: CONFIG_CREATE_ARCH_SYMLINK "
dgriego has quit [Client Quit]
sakoman has joined #yocto
dgriego has joined #yocto
ljh has joined #yocto
ccf has quit [Quit: Leaving.]
dgriego has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dgriego has joined #yocto
leon-anavi has quit [Quit: Leaving]
dgriego has quit [Client Quit]
dgriego has joined #yocto
GNUmoon2 has quit [Remote host closed the connection]
GNUmoon2 has joined #yocto
dgriego has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]