<kevinrowland>
fray: what do you mean by python helpers? FWIF the package I depend on lands in `${RECIPE_SYSROOT}/usr/lib/python3.9/site-packages/` , which I think is a standard location
<kevinrowland>
s/FWIF/FWIW/
<khem>
RP: I wonder how to handle it, the patches are compressed gz files
<RP>
kanavin: I've sent a further patch for one of the sstate issues. I'm hoping this fixes the other issue we were seeing as an intermittent autobuilder failure
tnovotny has quit [Ping timeout: 240 seconds]
vladest has quit [Remote host closed the connection]
vladest has joined #yocto
danlor has joined #yocto
lexano has joined #yocto
sakman_ is now known as sakman
<jclsn>
rburton: Thanks :)
bluelightning has quit [Server closed connection]
bluelightning has joined #yocto
Daanct12 has quit [Quit: WeeChat 4.1.1]
<kanavin>
RP: thanks, I sent a confirmation on the ML
tnovotny has joined #yocto
<RP>
kanavin: I did also get confirmation from michael that sstate artefacts were being delted as unused which explains some of the other issues. Hopefully the two fixes together will help resolve things.
<RP>
kanavin: this still leaves the questions about the CDN population but perhaps things are related ?
<kanavin>
RP: we should re-enable those tests. The tricky part is that sstate population happens in different builder, and if that is successful, the build and all traces of what it did is erased (thanks to my other patch to AB :-D. I'm thinking of adding qemux86-64/qemuarm64 steps into 'yocto-mirror' builder, but maybe we could do something else to aid debugging (if still needed).
<kanavin>
RP: I'm running out to a dentist appointment :)
vladest has quit [Remote host closed the connection]
vladest has joined #yocto
<dvergatal>
hey guys I have finally disocvered the issue about the problem I mentioned yesterday
<dvergatal>
actually ca-certificates-native is not installing ca-certificates.crt into recipe-sysroot-native/etc/ssl/certs for curl-native and any other native package
simond4722 has quit [Quit: Ping timeout (120 seconds)]
rfried has quit [Quit: Ping timeout (120 seconds)]
rfried has joined #yocto
simond4722 has joined #yocto
<dvergatal>
question is why because in sstate cache populate_sysroot in tar file for native I see all certificate files even if I have hardcoded in do_install:append:class-native to install this file ca-certificates.crt it is not being installed for curl-native in recipe-sysroot-native
jmd has quit [Ping timeout: 248 seconds]
jmd has joined #yocto
zpfvo has quit [Quit: Leaving.]
ardo has quit [Ping timeout: 240 seconds]
ardo has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
Kubu_work has quit [Quit: Leaving.]
florian_kc has joined #yocto
xmn has quit [Quit: ZZZzzz…]
florian_kc has quit [Ping timeout: 255 seconds]
xmn has joined #yocto
frieder has quit [Remote host closed the connection]
Chocky1 has quit [Quit: Leaving.]
Chocky has joined #yocto
Haxxa has quit [Quit: Haxxa flies away.]
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #yocto
Vonter has quit [Ping timeout: 245 seconds]
Vonter has joined #yocto
Haxxa has joined #yocto
Chaser_ has quit [Ping timeout: 255 seconds]
Chaser has joined #yocto
florian_kc has joined #yocto
Chaser has quit [Quit: Chaser]
Vonter has quit [Ping timeout: 240 seconds]
Vonter has joined #yocto
goliath has joined #yocto
sakoman has quit [Ping timeout: 252 seconds]
sakoman has joined #yocto
alessioigor has quit [Quit: alessioigor]
prabhakar has joined #yocto
lexano has quit [Remote host closed the connection]
lexano has joined #yocto
jmd has quit [Remote host closed the connection]
tleb has quit [Remote host closed the connection]
tleb has joined #yocto
prabhakarlad has quit [Quit: Client closed]
Vonter has quit [Ping timeout: 252 seconds]
tnovotny has quit [Read error: Connection reset by peer]
tnovotny has joined #yocto
goliath has quit [Quit: SIGSEGV]
sakoman has quit [Ping timeout: 252 seconds]
Chocky has quit [Quit: Leaving.]
Chocky has joined #yocto
Chocky has quit [Client Quit]
Chocky has joined #yocto
sakoman has joined #yocto
Xagen has joined #yocto
leon-anavi has quit [Quit: Leaving]
mvlad has quit [Remote host closed the connection]
lexano has quit [Remote host closed the connection]
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
r00tkit has joined #yocto
goliath has joined #yocto
Minvera has quit [Ping timeout: 255 seconds]
<r00tkit>
Hi, can someone help me understand why I am getting an error like- "/usr/bin/xyz contained in package demo requires libPocoNet.so.95()(64bit), but no providers found in RDEPENDS:demo? ", even though I have added DEPENDS = "poco" inside the demo package recipe. Poco is installed via meta-oe layer.
rber|res has quit [Ping timeout: 255 seconds]
rber|res has joined #yocto
sudip has quit [Server closed connection]
sudip has joined #yocto
<ente>
r00tkit: do you have something like RDEPENDS_${PN} = "poco" ?
<r00tkit>
Nope, do I need to add that in my .bb file?
<ente>
I suppose
<r00tkit>
Ok, let me try. As per Yocto KB, I thought having DEPENDS is enough to resolve the runtime dependency too
<Saur>
It works if bitbake can determine the runtime dependency from the ELF files.
<r00tkit>
still no luck. Same error!
<r00tkit>
Got both the lines in the .bb file-
<r00tkit>
DEPENDS = "poco" \\
<r00tkit>
RDEPENDS_${PN} = "poco"
<ente>
is it DEPENDS= or DEPENDS_${PN}=?
<ente>
I should sleep before I make it worse :)
<ente>
also are you sure that the .so file in question is part of the package?
<r00tkit>
No worries, appreciate the leads. Looks like a long night at my end
<ente>
maybe pocoNet is a separate package, I wouldn't know
<ente>
good luck!
<r00tkit>
Yep, found the issue. On my build machine, seems like I have a newer .so version of Poco (libPocoZip.so.95), the one in meta-oe still uses *so.94.
<r00tkit>
thanks for the hint!
<Saur>
r00tkit: That sounds as if your application has been linked with the host library rather than the target library produced by bitbake. That is definitely an error in either the applications recipe, or its build configuration.
<r00tkit>
I want to fetch the pre-compiled binary from host, not compile it in Yocto
<r00tkit>
the Poco version on build is 1.12.5p1, meta-oe provides 1.12.4
<Saur>
Well, now you know why that is generally a bad idea. ;)
<r00tkit>
I mean, this is going to be the use case- I am building a closed source software :)
<Saur>
Not sure what that has to do with anything. The majority of the recipes in our products are proprietary.
<r00tkit>
How am I supposed to compile it on my side other than the usual cmake process where I install Poco and then dynamically link my binary against it, before letting customer fetch it in their Yocto recipe?
sakoman has quit [Ping timeout: 255 seconds]
sakoman has joined #yocto
<Saur>
Ah, you are building an application that you will deliver as a binary. I thought you were building it for yourself.
<r00tkit>
Exactly
florian_kc has quit [Ping timeout: 264 seconds]
<Saur>
I guess it depends on the situation. You can of course build it statically, with the drawback it gets bigger. Or you need to make sure you build it with the same versions of the dependencies as the customer has. Depending on the libraries, you may also get away with building using older versions. I.e., if you want to make a binary as compatible as possible, you typically want to build it using the oldest environment rather than the newest
<Saur>
since libraries are typically backwards compatible, but very few are forwards compatible. ;)