kscherer has quit [Quit: Konversation terminated!]
manuel_ has quit [Ping timeout: 260 seconds]
davidinux has quit [Ping timeout: 260 seconds]
davidinux has joined #yocto
kpo has joined #yocto
sakoman has quit [Quit: Leaving.]
kpo has quit [Ping timeout: 250 seconds]
<vmeson>
I have a new 20 core, 32 GB, 1 TB SSD laptop that I setup with an encrypted filesystem. bitbake world seemed fast enough initially but on the 4th world build, it's really slow! Anyone have experience with builds on encrypted FS?
<vmeson>
I didn't clean-up between builds so the 1 TB SSD is about 80% of capacity.
* vmeson
calls it a day.
nemik has quit [Ping timeout: 245 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 245 seconds]
nemik has joined #yocto
jclsn has quit [Ping timeout: 246 seconds]
jclsn has joined #yocto
sakoman has joined #yocto
diamondman__ has quit [Server closed connection]
diamondman__ has joined #yocto
Thorn has joined #yocto
sgw has quit [Ping timeout: 240 seconds]
Xagen has joined #yocto
sgw has joined #yocto
hays has joined #yocto
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Xagen has joined #yocto
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<JaMa>
vmeson: I was using TMPDIR on unencrypted partition to avoid these issues and removed TMPDIRs when laptop wasn't safely at home, but it sucks if you travel often :)
florian_kc has quit [Ping timeout: 240 seconds]
BCMM has joined #yocto
amitk_ has joined #yocto
LetoThe2nd has quit [Server closed connection]
LetoThe2nd has joined #yocto
nerdboy has quit [Ping timeout: 245 seconds]
<LetoThe2nd>
yo dudX
<mckoan>
LetoThe2nd: hey o/
amitk_ has quit [Ping timeout: 240 seconds]
nerdboy has joined #yocto
nerdboy has quit [Changing host]
nerdboy has joined #yocto
Yrrsinn[m] has joined #yocto
<Yrrsinn[m]>
I am trying to add nativesdk-python3-tkinter to my SDK,
<Yrrsinn[m]>
add a receipes-devtools/python/python3_%.bbappend with PACKAGECONFIG_class-nativesdk_append_pn-python3 = " tk",
<Yrrsinn[m]>
but the _tkinter.cython.*.so is not created nor packed during the build.
<Yrrsinn[m]>
What did I forget?
<JaMa>
Yrrsinn[m]: use bitbake -e to check PACKAGECONFIG value
<JaMa>
Yrrsinn[m]: or bitbake-getvar
rfuentess has quit [Remote host closed the connection]
ChrysDaze has joined #yocto
<ChrysDaze>
Hi:) I'm doing an Image for an IMX8MM using Yocto on kirkstone. I'm also trying to compile a m4 binary to put into my rootfs via a layer found on web. And I get an error when I try to add through IMAGE_INSTALL the recipe from this m4 binary. Here is the message : https://pastebin.com/077nj3zs
<ChrysDaze>
Thanks in advance.
fullstop has quit [Server closed connection]
fullstop has joined #yocto
amitk_ has joined #yocto
<mckoan>
ChrysDaze: definitely too few info to help
<ChrysDaze>
@Mcko
<ChrysDaze>
mckoan that's the point to. I have not more info than that.
<ChrysDaze>
The logs are really small
d-s-e has joined #yocto
<barath>
someone here have experience with qttools/linguist and sdks? there's a patch for qttools which makes the path to for instance the lrelease binary work, but it's only applied if you build the recipe as non-native or non-nativesdk, so wondering if I'm doing something wrong of whether the qttools recipe might need a SRC_URI:append:class-nativesdk for the patch
<ChrysDaze>
The recipe works in itself to build the binary, but seems not working when doing IMAGE_INSTALL.
<ChrysDaze>
I've already done myself a recipe to add things in the rootfs in a similar manner, and doesn't have this problem of "populate_sdk". I've removed my sstate-cache, sstate, tmp folder to go from begginning
<ChrysDaze>
I'm able to build the mcuxhelloworld example by itself doing bitbake mcuxhelloworld
<SheatNoisette>
What's weird. mcuxhelloworld was designed for the Boundary Device Nitrogen series initially
<ChrysDaze>
I'm working in a IMX8MM Based boards
<ChrysDaze>
When I read the recipe, it's compile and then add it to the rootfs somewhere. I don't understand why the populate_sdk of the image claim the do_package_write_ipk.
<ChrysDaze>
When i have already done the binary and just do a recipe which send the binary to the rootfs I have no problem :/
<SheatNoisette>
What I don't understand is why yocto fails to do_package_write_ipk with it
<ChrysDaze>
That's why also i'm confused
<SheatNoisette>
This doesn't make any sense
<ChrysDaze>
I've cleaned my workdir, by removing the tmp, sstate-cache and downloads directory
<SheatNoisette>
You tried to build a sdk ?
<ChrysDaze>
I tried also yes
<ChrysDaze>
The error came at the beggining of the build process, juste after parsing recipes.
<SheatNoisette>
I'm trying to reproduce the issue
<SheatNoisette>
I'll make a clean project. The one i'm working with is filled with other packages.
<ChrysDaze>
Ok thanks
<SheatNoisette>
(This will take a while)
<ChrysDaze>
Maybe to reproduce, can you try with the meta-arm-toolchain?
<ChrysDaze>
in your repo there is not the recipe for the cross compiler
<ChrysDaze>
So instead of doing the recipe by myself, i've took the one by the meta-arm-toolchain
<ChrysDaze>
The last things i've done is "TOOLCHAIN_TARGET_TASK:remove = " mcuxhelloworld""
<ChrysDaze>
Which seems to avoid this eror
<ChrysDaze>
So yeah linked to this native!
camus has quit [Remote host closed the connection]
<ChrysDaze>
Merci pour votre aide yocton et @shea
<ChrysDaze>
Trying this now :)
xmn has quit [Quit: ZZZzzz…]
xmn has joined #yocto
prabhakarlad has quit [Quit: Client closed]
Xagen has joined #yocto
|Xagen has joined #yocto
<vmeson>
rburton: JaMa : yes I'll probably re-install and not use an encrypted FS. Of course, I'd like to understand why build time is degrading. There are other variables (PSI) in play but previous runs with lower limits on PSI were MUCH FASTER!
Xagen has quit [Ping timeout: 252 seconds]
sakoman has joined #yocto
kscherer has joined #yocto
alessioigor has quit [Remote host closed the connection]
<Guest53>
Hello, what is the best way to do `loginctl enable-linger $USER` by yocto? to enable linger for a user from the flash. I don't find where to put this configuration into a file, only the command line to do it. Is it the same rebuild systemd with `--without-kill-user-processes` option?
florian_kc has quit [Ping timeout: 240 seconds]
SheatNoisette has quit [Ping timeout: 246 seconds]
florian_kc has joined #yocto
vmeson has quit [Quit: Konversation terminated!]
vvmeson has joined #yocto
florian_kc has quit [Ping timeout: 260 seconds]
kscherer has quit [Quit: Konversation terminated!]
<RP>
mario-goulart: was it an AB-INT search on bugzilla?
<mario-goulart>
RP: could have been. I didn't see how rburton reached the page. :-)
<mario-goulart>
Ah, yes. A search for AB-INT does give more results. Thanks, RP.
florian_kc has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
<RP>
mario-goulart: it is a topic I spend far too much time on! :/
nemik has joined #yocto
<mario-goulart>
I'm trying to find issues that might be related to race conditions in the build system of the components built by recipes. With those, I'd try to see if landlock make could help spot potential issues in the makefiles.
Wouter0100670440 has quit [Read error: Connection reset by peer]
Wouter0100670440 has joined #yocto
<RP>
mischief: no duplicate tasks so it isn't what I'd wondered about :/
sakoman has quit [Quit: Leaving.]
<RP>
mario-goulart: I wonder if there are ways we could use the landlock LSM inside pseudo for example
amitk has quit [Ping timeout: 264 seconds]
sakoman has joined #yocto
<mischief>
RP: if i run with -k there are a number of recipes failing, and they seem to have a theme in common that it is always files marked without write permission
<mischief>
i wonder if this is because of a change in tar..
<RP>
mischief: it could even be a bug in tar I guess :/
<mischief>
RP: well, the hosts uses ubuntu 18.04 lts which is perhaps a "old" tar 1.29 from like 2015. i plan (soon) to upgrade to 22.04 which has a bit newer version, though we also have to fix some problems with linux backports and coccinelle for that ;-)
sgw has quit [Remote host closed the connection]
<RP>
mischief: can you inject a buildtools tarball into your build? I think that should have a more recent tar in it
<mischief>
i was thinking that too, worth a try
<RP>
mischief: it would be interesting to see if it changed things
<mischief>
we have to do if we try using amazonlinux, since the tar there is absolutely ancient
<mischief>
have to do that anyway*
sgw has joined #yocto
<mischief>
unfortunately no luck
<RP>
mischief: :(
<RP>
mischief: which release of the project is this with?
<mischief>
i tried using 4.0.10 buildtools-extended-nativesdk
<mischief>
RP: we're on kirkstone 4.0.10, so i picked buildtools to match it.
<mischief>
unfortunately i didn't repro this locally which is also weird :) only in our ci