<jclsn>
I will create the workspace again and see if that .config file differs from the defconfig
frieder has joined #yocto
goliath has joined #yocto
wooosaiiii is now known as wooooo
wooooo is now known as wooosaiiii
Starfoxxes has joined #yocto
<jclsn>
Ah guess that is some general .config file from mainline linux, as it contains 6000+ lines
<jclsn>
The defconfig in the workspace is the same as in my kernel recipe
<jclsn>
I can't find one in build/tmp/work-shared/vti1/kernel-source though
rfuentess has joined #yocto
<RP>
khem: You must be covering ppc64, mips and musl combinations we're not?
mvlad has joined #yocto
Schlumpf has joined #yocto
prabhakarlad has joined #yocto
tre has joined #yocto
jaydeep51[m] has joined #yocto
prabhakarlad has quit [Quit: Client closed]
tprrt has joined #yocto
florian has joined #yocto
ejo has joined #yocto
<rburton>
khem: yeah all good, thanks
tprrt is now known as tperrot
<ejo>
Hi, is there a way to change the back-end of a dependency without changing it for the whole project? For example in recipe A.bb I want to use curl in DEPENDS with wolfssl instead of gnutls and in recipe B.bb I want to use curl _with_ gnutls. I.E. I don't want to set PACKAGECONFIG[gnutls] = "--without-gnutls" and EXTRA_OECONF = "--with-wolfssl"
<ejo>
in curl_%.bbappend because that changes it for both A.bb and B.bb, is there a way to set PACKAGECONFIG and EXTRA_OECONF for curl in A.bb?
kroon has joined #yocto
<qschulz>
ejo: this is usually understood as a policy decision
<qschulz>
and policy decisions are put into distro configuration files
<qschulz>
if you want wolfssl curl AND gnutls curl AT THE SAME TIME in the SAME IMAGE, then 1) I don't know if that is technically possible
<qschulz>
2) you could use a slightly renamed curl recipe (e.g. curl-wolfssl) which would replace "normal" curl recipe in your A or B recipe
<ejo>
Thanks for the answer! in this case recipe A will only be built for native, and A will be used as a signing tool.
<ejo>
Option 2 was my idea too, so I think I'll go with that
<qschulz>
ejo: you can have a different option for native and target packages
<qschulz>
the :class-target and :class-native overrides are for that
<qschulz>
e.g. PACKAGECONFIG:class-native = "wolfssl"
<qschulz>
would override completely the "default" PACKAGECONFIG
leon-anavi has joined #yocto
xmn has quit [Ping timeout: 256 seconds]
Schlumpf has quit [Ping timeout: 256 seconds]
starblue has quit [Ping timeout: 250 seconds]
starblue has joined #yocto
Schlumpf has joined #yocto
roussinm has joined #yocto
roussinm has quit [Client Quit]
prabhakarlad has joined #yocto
rob_w has quit [Ping timeout: 250 seconds]
florian_kc has joined #yocto
rob_w has joined #yocto
roussinm has joined #yocto
florian_kc has quit [Ping timeout: 252 seconds]
sotaoverride has joined #yocto
<sotaoverride>
can someone please remind me how we can get image recipes to generate checksums for all atrifacts that the recipe makes?
<vvn>
how do you guys usually edit the fstab? bbappend base-files? image postprocess function? wks only?
<sotaoverride>
qschulz: Thanks!
wooosaiii has quit [Remote host closed the connection]
tre has joined #yocto
rob_w has quit [Remote host closed the connection]
tlhonmey has joined #yocto
kroon has quit [Quit: Leaving]
manuel1985 has joined #yocto
<rburton>
RP: just sent a little cleanup for setuptools-rust-native
AKN has joined #yocto
<vvn>
which package must provide /etc/crypttab?
<mckoan>
vvn: cryptsetup ?
<vvn>
it feels like it yea
tre has quit [Remote host closed the connection]
manuel1985 has quit [Ping timeout: 260 seconds]
<moto-timo>
sgw: poky commit 5b4aab6b40c
<moto-timo>
sgw: kernel: Add support for multiple kernel packages
<moto-timo>
rburton: last time I tried setuptools_build_meta with python3-setuptools-rust-native the wheel was named UNKNOWN-0.0.0-*.whl did that get fixed?
<rburton>
yes
<rburton>
got the proper name (and it installs with a glob anyway)
<moto-timo>
rburton: and thank you for the cleanup... I knew it was needed but the stuff you were dooing was still in flux
<moto-timo>
rburton: excellent. thank you,
<rburton>
i also ran diffoscope on the generated sysroot
<moto-timo>
\o/
* moto-timo
flushes that cache
xmn has joined #yocto
<moto-timo>
rburton: I see you had already answered my question in the commit log… clearly more coffee is required this morning
<qschulz>
RP: michaelo: re doc building on the autobuilder. The patch series I just sent should fix all warnings reported by sphinx v3.2.1
florian has quit [Quit: Ex-Chat]
<qschulz>
RP: michaelo: the question is should I also add patches for newer version of sphinx? e.g. 4.4.0 (the latest version) complains for Honister branches
<qschulz>
or do we fix this the day we upgrade sphinx on the autobuilder and we don't care for now?
Schlumpf has quit [Quit: Client closed]
leon-anavi has quit [Quit: Leaving]
<RP>
qschulz: I'd think we'd want to fix the later issues too if we can
jmiehe has joined #yocto
<RP>
qschulz: do they cause problems in older versions?
rfuentess has quit [Remote host closed the connection]
<rburton>
zeddii: just sent some devupstream patches to oe-core. as the kernel is the only user in oe-core it would be appreciated if you could double check they're doing the right thing
<qschulz>
RP: just to be clear, I'm talking about yocto-autobuilder-helper and not the docs themselves. The docs themselves should be fixed ASAP.
<qschulz>
RP: for now the new warning is just about using directives instead of hardcoding links, so that is not an issue for older sphinx
<RP>
qschulz: I can't remember which workers we run sphinx on and how easily we can choose the sphinx verison there
mckoan is now known as mckoan|away
florian_kc has joined #yocto
frieder has quit [Remote host closed the connection]
<sakoman>
khem: yes, I'll add that to my test queue
AKN has quit [Read error: Connection reset by peer]
<khem>
RP: yes I have few jobs intentionally set to test the combinations that yocto does not test to widen the coverage and especially with LTS trying to get to the issues usually which are ignored
yannd has joined #yocto
florian_kc has joined #yocto
florian_kc has quit [Ping timeout: 250 seconds]
akiCA has joined #yocto
ejo has quit [Ping timeout: 256 seconds]
jmiehe has quit [Quit: jmiehe]
florian_kc has joined #yocto
prabhakarlad has quit [Quit: Client closed]
manuel1985 has joined #yocto
<sielicki>
Should we consider journald as a syslog provider in 2022? It's not really a syslog implementation in the sense of rsyslog/syslog-ng, but I think it would be intuitive for someone to be able to set `VIRTUAL-RUNTIME:syslog = "systemd-journald"` to get a system where only systemd-journald runs.
<sielicki>
The mere fact that journald has an option called, "ForwardToSyslog" betrays the fact that he doesn't think of himself as a syslog implementation.
<sielicki>
s/The/That/, s/mere fact that//
GillesM has joined #yocto
GillesM has quit [Remote host closed the connection]