<Beartama>
yes, i have 2 issues, 1st is the `disable_network` function in bitbake not working which makes the build fails, and 2nd is the `quilt` package doesn't build also (some dependency problem) while it builds fine on Ubuntu 22.04
<Beartama>
i did only try Nanbield instead of Scarthgap though
michael_e has joined #yocto
amitk has joined #yocto
<Beartama>
same thing for Scarthgap actually
<mcfrisk_>
I presume openssl 3.3.0 pkg-config libdir change from /usr/lib to /usr is breaking build elsewhere too..
Beartama has quit [Quit: Client closed]
Vonter has joined #yocto
c-thaler has joined #yocto
enok has quit [Ping timeout: 245 seconds]
Beartama has joined #yocto
Beartama has quit [Quit: Client closed]
ThomasRoos has quit [Quit: Client closed]
enok has joined #yocto
sakoman has quit [Ping timeout: 268 seconds]
Vonter has quit [Read error: Connection reset by peer]
Vonter has joined #yocto
sakoman has joined #yocto
enok has quit [Quit: enok]
enok has joined #yocto
Beartama has joined #yocto
Saur_Home has quit [Quit: Client closed]
Saur_Home has joined #yocto
<rburton>
mcfrisk_: ouch wtf where?
<mcfrisk_>
rburton: at least in my config, all .pc files from openssl have libdir=/usr now. trying to patch it away. there is a new way to generate .pc and .cmake files.
<rburton>
master or scarthgap or what?
<mcfrisk_>
master
<rburton>
you'd have thought that wouldn't make it through the AB but you never know
<rburton>
give me five and i'll replicate or not
<mcfrisk_>
meta-security/meta-tpm tpm2-openssl failed to compile
enok has quit [Ping timeout: 255 seconds]
<mcfrisk_>
I presume a lot of openssl users hardcode /usr/lib and don't use pkg-config libdir
vladest has quit [Remote host closed the connection]
olani has quit [Remote host closed the connection]
locutusofborg_ has quit [Ping timeout: 256 seconds]
locutusofborg has joined #yocto
michael_e has quit [Quit: Client closed]
<mcfrisk_>
rburton: thanks! testing..
ajfriesen has joined #yocto
uy has joined #yocto
uy is now known as beartama
beartama has quit [Client Quit]
beartama has joined #yocto
beartama has quit [Client Quit]
beartama has joined #yocto
vladest has quit [Read error: Connection reset by peer]
xmn has joined #yocto
lexano has joined #yocto
c-thaler has quit [Quit: Client closed]
olani has joined #yocto
vladest has joined #yocto
jmiehe has joined #yocto
florian_kc has joined #yocto
jmiehe has quit [Client Quit]
enok has joined #yocto
Saur_Home has quit [Quit: Client closed]
Saur_Home has joined #yocto
ablu has quit [Ping timeout: 255 seconds]
<JaMa>
rburton: your change doesn't fix the empty prefix (failure for chip and matter), but I still like it much more than the .patch file, thanks
ablu has joined #yocto
<landgraf>
hmmm. nodejs is broken in meta-oe :-/ have to wait for the fix to be accepted now
ablu_ has joined #yocto
<JaMa>
you can backport the fix in your layer (like I did)
<landgraf>
I've done this already
<landgraf>
but not have to monitor upsteam to drop the backport :)
ablu has quit [Ping timeout: 252 seconds]
<landgraf>
JaMa: The fix works fine for me btw. We have quite a few npm packages in the layer.
<JaMa>
it works for me as well
Guest48 has joined #yocto
amurray_tgp has joined #yocto
ablu_ is now known as ablu
Guest48 has quit [Client Quit]
<amurray_tgp>
Hey, no bugs from me today, but i do have a question. When inheriting cve-check and building an image, e.g. core-image-sato.... you end up with two lists of CVEs:
<amurray_tgp>
I've interpreted the first as all the CVEs related to software included in the image
<amurray_tgp>
Is it correct to interpret the second as all the CVEs related to software that was built in order to create the (last) image (built)? (I.e. it may include -native packages that could have vulnerabilities, e.g. a compiler that builds vulnerable binaries)
<rburton>
thats an upstream bug, there is no prefix in the .pc files
<rburton>
file a bug with them about that
<JaMa>
there was in older openssl I believe, with new openssl it started to fail, that's why I've sent the PR
enok has joined #yocto
<JaMa>
"there is no prefix in the .pc files" grep -c ^prefix= ../lib32-recipe-sysroot/usr/lib*/pkgconfig/* | wc -l -> 77 "exceptions" just in chip's RSS :)
<JaMa>
and 73 more in native RSS
goliath has joined #yocto
<rburton>
in openssl's .pc file, i meant
<rburton>
99% do have it and i've no idea why openssl removed it
ecdhe_ is now known as ecdhe
<JaMa>
ah, ok
Guest48 has joined #yocto
jmiehe has joined #yocto
jmiehe has quit [Client Quit]
<JaMa>
beartama: how does `disable_network` and quilt build fail?
<rfs613>
k=$(expr $j + 1); i'm thinking it should be k=$(expr $k + 1);
<rfs613>
but not sure if I am missing some understanding...
<JaMa>
yes, look like copy&paste from L363
<rfs613>
as written, it ends up calling uboot_assemble_fitimage_helper multiple times with the *same* arguments (well, at least in the case where you have two entries in UBOOT_CONFIG)
<alperak>
ap6256 wifi/bt firmware seems to be used in many boards but it is not added to linux-firmware and is available in different repos. what makes sense to use as a license for this?
<rburton>
alperak: if you can't identify the license then that would be why its not in linux-firmware. if you can, submit it.
<alperak>
all right, i will try. thanks.
<JaMa>
beartama: are you using lxc or some container to run ubuntu or natively on host? I have it in docker
florian_kc has joined #yocto
goliath has quit [Quit: SIGSEGV]
<beartama>
jama: i'm running natively, no virtualization
vladest has quit [Remote host closed the connection]
KanjiMonster has quit [Remote host closed the connection]
KanjiMonster has joined #yocto
enok has quit [Ping timeout: 252 seconds]
Guest77 has joined #yocto
<Guest77>
We have installed a.camera management system on top of yocto kirkstone within a balena engine but we are unable to communicate with the wifi camera. We need to know if there is any specific configuration we may need on the yocto level for processing video?
Guest77 has quit [Client Quit]
Guest77 has joined #yocto
Guest77 has quit [Client Quit]
Guest77 has joined #yocto
<Guest77>
If you want to install camera system within a container on top of yocto do we need to configure yocto to be able to process videos on the board?
Guest77 has quit [Ping timeout: 250 seconds]
Kubu_work has quit [Quit: Leaving.]
alperak has quit [Quit: Connection closed for inactivity]
Guest77 has joined #yocto
Guest77 has quit [Quit: Client closed]
sakman_ has joined #yocto
Emantor_ has joined #yocto
sudip_ has joined #yocto
Hazza has joined #yocto
vmeson has joined #yocto
schtobia_ has joined #yocto
nots has joined #yocto
bantu_ has joined #yocto
qschulz_ has joined #yocto
sakman has quit [Remote host closed the connection]