ecdhe has quit [Read error: Connection reset by peer]
azcraft has joined #yocto
ecdhe has joined #yocto
goliath has joined #yocto
<brabander>
RP: about missing socket file, are there any reports of someone noticing this outside of the buildbot?
<brabander>
also maybe running inotify tools on the server could help provide information
sion33 has joined #yocto
<tomzy_0>
morining
<tomzy_0>
ehh.. morning ;)
<RobertBerger>
I built meta-zephyr for some cortex m4 and now I try to build a simple app with rust/cargo. But with the default class it pulls in the std lib instead of bare metal. Did someone manage to get this to work?
camus has quit [Read error: Connection reset by peer]
leon-anavi has joined #yocto
frieder has joined #yocto
camus has joined #yocto
Guestu has joined #yocto
<Guestu>
Hello, I would like to create a zip file with my image inside and some binaries a the end of the. Any hint to do that with yocto ? Post process is the best way ?
<hsv>
but the changes appear not to be present (using compiled in drivers).
<qschulz>
mrybczyn[m]: thanks, i've got to fill in papers for certification so I need to say "we fixed this" or "don't care because that's not in our threat model", so this info helps a lot :)
tor_ is now known as tor
<qschulz>
jonmason: update your conf to not use the ycotoproject mirrors as a premirror. I think we have a rate limit in place on the server when you download too often/too much at the same time?
<qschulz>
Guestu: I believe you need a new image type (look at what's done in image_types.bbclass)
<qschulz>
pretty sure we have documentation for this too
<qschulz>
hsv: not do it :)
<qschulz>
hsv: use devtool modify virtual/kernel
<rburton>
Guestu: you can create a custom image type which does that and then set eg IMAGE_FSTYPES = ext4.myzip. see image_types.bbclass
<RP>
brabander: I suspect most people would rerun the command and ignore it so it is hard to tell how widespread it is. We'd need to add inotify monitoring to all ~30 workers so it is a bit a of a pain to do
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<brabander>
RP, I was asking because it could be a hint that this might be an issue only on the buildbot, e.g. multiple jobs running at same time
<abelloni>
the problem is that this is tagged langdale
<RP>
abelloni: ah :/ It should work with master, I'll mention
<ThomasRoos[m]>
Is there any way to set QB_MEM only when building for specific MACHINE e.g. qemuarm64 in local.conf - something like QB_MEM:qemuarm64 = "-m 16384"
<mcfrisk>
I've leaked tens of Parser-[1-36] processes, seems to be some bitbake left overs..
<qschulz>
ThomasRoos[m]: I'd assume so, yes. Is it not working?
<ThomasRoos[m]>
just quessed - will try :D
<qschulz>
ThomasRoos[m]: although remember that local.conf should not be shared. It should be treated as a temporary configuration file (for e.g. development/debugging)
<qschulz>
ThomasRoos[m]: QB_MEM:qemuarm64 will completely override QB_MEM for qemuarm64 though
<qschulz>
you *might* have to precise for which recipe this applies to but I don't think it'll be needed
<qschulz>
(e.g. QB_MEM:pn-some-recipe:qemuarm64
<hsv>
'bitbake linux-ti-staging -f -c compile' works, whereas 'bitbake virtual/kernel -f -c compile' appears to miss changes in the sources.
<ThomasRoos[m]>
qschulz: thank you - problem is arm32 doesn't like that setting ;)
* hsv
understood that virtual/kernel was an alias for the targeted kernel.
<abelloni>
RP: to be clear, it has both the master and langdale tags but my filter did filter it out
<qschulz>
hsv: it's an alias if it's correctly set
<hsv>
maybe it's incorrectly set then.
<qschulz>
hsv: you should have a PREFERRED_PROVIDER_virtual/kernel set somewhere
bitob[m] has joined #yocto
seninha has joined #yocto
<hsv>
well now it works, so what i was doing wrong before is a mystery.
starblue1 has quit [Ping timeout: 252 seconds]
starblue1 has joined #yocto
Circuitsoft has quit [Quit: Connection closed for inactivity]
tomzy_0 has joined #yocto
pidge has joined #yocto
<kayterina[m]>
Hello, in our project we use external repositories, I mean meta-java, meta-python, poky. Where in the project can I check if these layers fetch a precompiled binary? I want to check if these repos keep any different cache than the other layers
<qschulz>
kayterina[m]: it's not entirely clear what you are looking for. what cache are you talking about, what "precompiled binary" are you talking about?
gho has quit [Quit: Leaving.]
gho1 has joined #yocto
gho1 has quit [Remote host closed the connection]
jmk1 has quit [Ping timeout: 256 seconds]
jmk44 has joined #yocto
<rburton>
kayterina[m]: if you want to audit the fetching then look at the SRC_URIs
seninha has quit [Remote host closed the connection]
rob_w has joined #yocto
tomzy_0 has quit [Quit: Client closed]
prabhakarlad has quit [Quit: Client closed]
leon has joined #yocto
leon is now known as Guest5714
leon-anavi has quit [Ping timeout: 252 seconds]
nemik_ has quit [Ping timeout: 272 seconds]
nemik_ has joined #yocto
mckoan is now known as mckoan|away
nemik_ has quit [Ping timeout: 252 seconds]
nemik_ has joined #yocto
Guestu has joined #yocto
<Guestu>
rburton qschulz thx for the reply about image_types.bbclass but all images are called after do_rootfs no ? The need is to put the generated image inside a zip ( so my image depends of previous one)
<qschulz>
Guestu: you want a zip inside your rootfs?
<Guestu>
qschulz Nop I just want to zip (and add password) a custom image (modified itb format). So in fact just call zip a the end of the image generation
<Guestu>
qschulz that's why I'm thinking about POST_PROCESS method (but I think it's the dirty way)
<qschulz>
Guestu: you can have some process after the image is created yes, or just (ab?)use the image_type mechanism
<qschulz>
it's not required to have an image type handle the full rootfs
<Guestu>
@qs
<Guestu>
qschulz image_type mechanism seems to be called after the image creation ( after rootf) so it's to earlier bc the image is no built yet
<qschulz>
Guestu: you can define image dependencies
<qschulz>
and have it created after the one image type you're interested in
sakoman has joined #yocto
ArgaKhan___ has quit [Remote host closed the connection]
ArgaKhan___ has joined #yocto
prabhakarlad has joined #yocto
zpfvo has quit [Ping timeout: 265 seconds]
kscherer has joined #yocto
<Guestu>
qschulz thx for support. All works with image_type mechanism:) except i'm not able to call git clone from the class, there is a workaround to clone a tiny repo during this step?
<qschulz>
Guestu: use a recipe for that?
<qschulz>
Guestu: we have disabled network access to all tasks in all recipes except do_fetch IIRC
<Guestu>
qschulz haaaa make sens, recipes are not just used to build an image ? an example of how to call recipe after image creation ? OMG i'm still learning about Yocto everyday :)
<Guestu>
ok I can call a recipe to deploy tools and play from deploy directory. Looks okay. Thank you again and sorry for wasting your time (again)
<qschulz>
Guestu: you have package recipes and image recipes
<qschulz>
package recipes build SW, image recipes create artifacts from those (usually rootfs)
<qschulz>
not entirely exact but good enough summary I think
<Guestu>
Ha ok I have to double check package recipe o.0
<qschulz>
Guestu: it's everything than isn't an image recipe
<qschulz>
(and has a .bb file extension)
<qschulz>
Guestu: not wasting anyone's time, don't worry
xmn has joined #yocto
<qschulz>
answering briefly (hopefully not harshly) because I'm fighting something else on my PC :)
<Guestu>
There is somewhere some infos about packages recipes ? because for me packages are just a group of recipes isn't ?
<Guestu>
qschulz developers fight everyday :P
zpfvo has joined #yocto
<qschulz>
Guestu: that's a packagegroup you're talking about
<qschulz>
we never call package recipes package recipes actually
<qschulz>
they are just "recipes"
<qschulz>
but so are image recipes, so we sometimes call them image recipes
<qschulz>
I like to distinguish them because they are not for the same purpose
<qschulz>
but they are both recipes indeed
<qschulz>
packagegroup is some special kind of package recipe which only define a set of packages to pull in if they are themselves pulled in the image by something