<khem>
I wonder where func_usage_message comes from, is your project using upstream
<khem>
or some vendor provided layers
lexano has quit [Ping timeout: 256 seconds]
jclsn has quit [Ping timeout: 240 seconds]
jclsn has joined #yocto
ablu has quit [Read error: Connection reset by peer]
ablu has joined #yocto
<yudjinn_>
khem: kirkstone, this is using the libtool recipe from poky
<yudjinn_>
from what I could gather, func_usage_message is supposed to just be... understood? idk I can never see a definition of it in any of the other software I found using it
enok has joined #yocto
enok has quit [Ping timeout: 264 seconds]
Thorn has quit [Ping timeout: 246 seconds]
Jones42 has joined #yocto
Thorn has joined #yocto
Jones42 has quit [Ping timeout: 268 seconds]
Thorn has quit [Ping timeout: 255 seconds]
Thorn has joined #yocto
Thorn has quit [Ping timeout: 268 seconds]
Thorn has joined #yocto
jmd has joined #yocto
Chaser has joined #yocto
amitk has joined #yocto
Chaser has quit [Ping timeout: 268 seconds]
leon-anavi has joined #yocto
prabhakalad has quit [Ping timeout: 264 seconds]
goliath has joined #yocto
frieder has joined #yocto
olani- has joined #yocto
mckoan|away is now known as mckoan
Kubu_work has joined #yocto
rfuentess has joined #yocto
michael_e has joined #yocto
Thorn has quit [Quit: Man who run behind car get exhausted]
mvlad has joined #yocto
prabhakalad has joined #yocto
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #yocto
destmaster has joined #yocto
<destmaster>
After updgrading my build from Kirkstone to Scarthgap I'm getting this error with SWupdate
<marex>
26d97acc7137 ("image-artifact-names: include ${IMAGE_NAME_SUFFIX} directly in both ${IMAGE_NAME} and ${IMAGE_LINK_NAME}")
<destmaster>
yes, new image have the rootfs suffix... I suppose that I need to add ".root in my bb , right?
<marex>
probably, I would assume your layer does use the image name somewhere, so that's where it has to be updated
<destmaster>
thanks!
<marex>
the aforementioned oe-core commit should also give you a hint what to grep for to find it
<marex>
sure
florian_kc is now known as florian
florian_kc has joined #yocto
qorin has joined #yocto
destmaster has quit [Remote host closed the connection]
yudjinn has joined #yocto
yudjinn_ has quit [Ping timeout: 240 seconds]
AdrianF7 has joined #yocto
AdrianF has quit [Ping timeout: 260 seconds]
kilobyte_ch has quit [Ping timeout: 260 seconds]
AdrianF7 is now known as AdrianF
DvorkinDmitry has joined #yocto
kilobyte_ch has joined #yocto
qorin has quit [Ping timeout: 250 seconds]
Daanct12 has quit [Quit: WeeChat 4.3.2]
jmiehe has joined #yocto
jmiehe has quit [Client Quit]
frieder has quit [Remote host closed the connection]
sugoi has quit [Ping timeout: 255 seconds]
olani- has quit [Remote host closed the connection]
mbulut has quit [Ping timeout: 240 seconds]
frieder has joined #yocto
mckoan is now known as mckoan|away
jmiehe has joined #yocto
michael_e has quit [Quit: Client closed]
sakoman has quit [Ping timeout: 264 seconds]
luc4 has joined #yocto
<luc4>
Hello! I noticed that, for some reason, /dev/ttyS0 is not readable by tty: crw--w---- 1 root tty 4, 64 Sep 20 11:25 /dev/ttyS0. Any idea why? I tried to create a udev rule to make it readable, but something keeps resetting it. What is the proper way to do this? Thanks!
michael_e has joined #yocto
sakoman has joined #yocto
JPEW has quit [Ping timeout: 256 seconds]
JPEW_ has joined #yocto
tortoise has quit [Ping timeout: 255 seconds]
NishanthMenon has quit [Ping timeout: 255 seconds]
Tartarus has quit [Ping timeout: 255 seconds]
jkridner has quit [Ping timeout: 255 seconds]
dl9pf has quit [Ping timeout: 268 seconds]
bradfa has quit [Ping timeout: 255 seconds]
mithro has quit [Ping timeout: 255 seconds]
nohit has quit [Ping timeout: 256 seconds]
moto-timo has quit [Ping timeout: 256 seconds]
ndec has quit [Ping timeout: 256 seconds]
smurray has quit [Ping timeout: 264 seconds]
denix has quit [Ping timeout: 264 seconds]
xtopher has quit [Ping timeout: 240 seconds]
reatmon has quit [Ping timeout: 268 seconds]
mdp has quit [Ping timeout: 268 seconds]
jwinarsk has quit [Ping timeout: 268 seconds]
jonmason has quit [Ping timeout: 256 seconds]
flynn378 has quit [Ping timeout: 256 seconds]
shivamurthy has quit [Ping timeout: 255 seconds]
georgem has quit [Ping timeout: 255 seconds]
praneeth_ has quit [Ping timeout: 256 seconds]
CosmicPenguin has quit [Ping timeout: 272 seconds]
madisox_ has quit [Ping timeout: 256 seconds]
rsalveti has quit [Ping timeout: 256 seconds]
elfenix|cloud has quit [Ping timeout: 256 seconds]
rhadye has quit [Ping timeout: 256 seconds]
kergoth_ has quit [Ping timeout: 256 seconds]
awafaa has quit [Ping timeout: 256 seconds]
wmills has quit [Ping timeout: 256 seconds]
diamondman__ has quit [Ping timeout: 256 seconds]
Crofton has quit [Ping timeout: 256 seconds]
rmmr has quit [Ping timeout: 255 seconds]
armpit has quit [Ping timeout: 255 seconds]
halstead has quit [Ping timeout: 255 seconds]
khazakar has quit [Ping timeout: 246 seconds]
LetoThe2nd has quit [Ping timeout: 264 seconds]
ernstp has quit [Ping timeout: 256 seconds]
paulbarker has quit [Ping timeout: 256 seconds]
rburton has quit [Ping timeout: 256 seconds]
ldywicki has quit [Ping timeout: 256 seconds]
darknighte has quit [Ping timeout: 256 seconds]
JPEW_ has quit [Ping timeout: 265 seconds]
patersonc has quit [Ping timeout: 268 seconds]
jonmason has joined #yocto
flynn378 has joined #yocto
ndec has joined #yocto
reatmon has joined #yocto
awafaa has joined #yocto
diamondman__ has joined #yocto
rhadye has joined #yocto
smurray has joined #yocto
georgem has joined #yocto
ldywicki has joined #yocto
NishanthMenon has joined #yocto
rsalveti has joined #yocto
wmills has joined #yocto
jwinarsk has joined #yocto
tortoise has joined #yocto
mithro has joined #yocto
dl9pf has joined #yocto
elfenix|cloud has joined #yocto
Crofton has joined #yocto
Tartarus has joined #yocto
rmmr has joined #yocto
bradfa has joined #yocto
praneeth_ has joined #yocto
darknighte has joined #yocto
patersonc has joined #yocto
madisox_ has joined #yocto
kergoth_ has joined #yocto
mdp has joined #yocto
jkridner has joined #yocto
xtopher has joined #yocto
LetoThe2nd has joined #yocto
shivamurthy has joined #yocto
denix has joined #yocto
armpit has joined #yocto
halstead has joined #yocto
moto-timo has joined #yocto
CosmicPenguin has joined #yocto
paulbarker has joined #yocto
rburton has joined #yocto
nohit has joined #yocto
JPEW_ has joined #yocto
ernstp has joined #yocto
lexano has joined #yocto
khazakar has joined #yocto
JPEW_ has quit [Ping timeout: 256 seconds]
JPEW_ has joined #yocto
JPEW_ has quit [Read error: Connection reset by peer]
JPEW_ has joined #yocto
sugoi has joined #yocto
sugoi has quit [Ping timeout: 255 seconds]
MrCryo has joined #yocto
rfuentess has quit [Read error: Connection reset by peer]
rfuentess has joined #yocto
Minvera has joined #yocto
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
goliath has quit [Quit: SIGSEGV]
Xagen has joined #yocto
mvlad has quit [Remote host closed the connection]
Guest65 has joined #yocto
xmn has joined #yocto
jmiehe has quit [Quit: jmiehe]
<luc4>
Hello! What is the proper way to disable or remove the service serial-getty@ttyS0.service in my image? Thanks!
jmiehe has joined #yocto
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Xagen has joined #yocto
<RP>
luc4: probably the SERIAL_CONSOLES variable?
<luc4>
RP: I tried that, but did not seem to work. Do I have to clean something maybe after adding it?
luca_ has joined #yocto
luc4 has quit [Ping timeout: 256 seconds]
luca_ is now known as luc4
<rburton>
luc4: thats a standard systemd service. you can bbappend the recipe to disable it
<luc4>
rburton: I tried adding this: sed -i -e "s/enable getty@.service/disable getty@.service/g" ${D}${systemd_unitdir}/system-preset/90-systemd.preset, but did not work. Is this what you are referring to?
<rburton>
luc4: i meant to use systemctl to disable it with the tooling
<luc4>
rburton: the image is readonly, can I do that with a command?
<rburton>
luc4: you should be able to use systemctl to disable it inside do_install
<luc4>
rburton: you mean in a file named systemd_%.bbappend?
<rburton>
yes
<luc4>
rburton: I'll try that as well then, thanks!
jmiehe has quit [Remote host closed the connection]
jmiehe1 has joined #yocto
jmiehe1 has quit [Read error: Connection reset by peer]
jmiehe has joined #yocto
jmiehe has quit [Client Quit]
jmiehe has joined #yocto
<luc4>
rburton: do you think I should disable serial-getty@ttyS0.service? Do you think that service is known while building the image?
<rburton>
yes. you _might_ need to do that in a new postinst but that can happen at rootfs time.
<luc4>
rburton: isn't there a way to disable all those services? Cause I also see the same for ttyAMA0.
<rburton>
tbh you can probably just delete serial-getty@.service
<Tyaku>
Hello, Recently we talk about how to replace bash (GPLv3) by something else. We said that busybox was not a good option because it has not been updated since some times and then we talk about zsh.
<Tyaku>
Question about zsh: does the package zsh provide ls, mkdir and this kind of functions ?
<rburton>
i still disagree that busybox isn't a good option: if you're refusing to use software because it's not made a release in less than a year i expect you'll struggle to get a bootable system
<rburton>
no, zsh is a shell, like bash
<Jookia>
Tyaku: busybox is a very good option and GPLv2, it provides those functions
<rburton>
note that its not sh compatible and unless you rewrite a lot of code you'll still need a provide sh, which is normally busybox
<Tyaku>
Because these functions are defined in busybox
<rburton>
Tyaku: "BusyBox is a software suite that provides several Unix utilities in a single executable file. "
<Jookia>
shells are meant to let you type in commands and run programs
<rburton>
busybox provide sh, ls, grep, etc etc. its small and lean. the "proper" gnu implementations of those are in coreutils, findutils, etc.
<rburton>
Tyaku: if you don't want gpl3 then don't install bash. busybox sh is good enough for most things, and if you find scripts that need bash then you either need to change your opinion on gpl3 or rewrite the script to be posix sh not bash
<luc4>
rburton: it seems I cannot call "disable", I'm getting systemctl: error: argument command: invalid choice: 'disable'.
<rburton>
ah our stub systemctl doesn't support disable, shame.
<rburton>
'rm' :)
<luc4>
rburton: the file does not seem to be there
<luc4>
It seems weird that removing an unwanted systemd service is this complex. I lost a day for it.
<rburton>
hard to tell when i can't see what you're doing
<rburton>
follow the dependencies, it's not on by default
<rburton>
the service file is in the systemd recipe, just delete the file
rfuentess has quit [Remote host closed the connection]
<Tyaku>
rburton: I have to watch it, because some days ago here, somebody talk about a couple of vulnerabilities reported and busybox not updated since long time.
<luc4>
rburton: you mean this one? ${D}${systemd_system_unitdir}/serial-getty@.service
<rburton>
luc4: yes
<luc4>
rburton: rm: cannot remove '/home/lcarlon/test/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/systemd/254.4/image/usr/lib/systemd/system/serial-getty@.service': No such file or directory
<rburton>
Tyaku: i never saw what the vulns were so can't comment
<luc4>
rburton: I'll use rm -f, but I guess it is not useful.
<Jookia>
Tyaku: FWIW there is always going to be vulnerabilities in software, we just don't know about them. what matters more is the overall architecture of your project, not individual components
<luc4>
rburton: according to that code however I'd say the SERIAL_CONSOLES trick should be sufficient... weird...
<Jookia>
in practice most projects will never even let people run busybox commands on their hardware
<rburton>
luc4: there are two implementations of the serial gettys - either the ones in systemd or the ones from the standalone systemd-serialgetty recipe
<luc4>
rburton: at this point, I'll probably go with killing the service when the image starts, can't find the proper way. Thanks for your help!
<rburton>
luc4: are you enabling serial-getty-generator in systemd?
<luc4>
rburton: I'm doing nothing related to this explicitly.
<luc4>
rburton: maybe a consequence of something else... not sure.
jmiehe has quit [Quit: jmiehe]
<rburton>
luc4: ah the use of the external one is the default, that's why. bbappend systemd-serialgetty to add a postinst and mask out the unit, or just change the depends in the systemd recipe to not pull in the systemd-serialgetty package at all
<luc4>
rburton: I'll try both, thanks!
frieder has quit [Remote host closed the connection]
<moto-timo>
vmeson: getting that to work will make a lot of cleanup of old ecj -> icedtea7 -> openjdk bootstrapping become "obsolete" (unless people are still actively using openjdk8)
dgriego has quit [Quit: Computer going to sleep]
Guest0 has joined #yocto
<Guest0>
how can i run yocto built binary amd64 unit tests for custom application on an ubuntu amd64 machine?
<Guest0>
*hello
yudjinn_ has joined #yocto
yudjinn has quit [Ping timeout: 240 seconds]
Kubu_work has quit [Quit: Leaving.]
jmiehe has joined #yocto
jmiehe has quit [Client Quit]
ctraven has joined #yocto
jmiehe has joined #yocto
jmiehe has quit [Client Quit]
yudjinn_ has quit [Remote host closed the connection]
mbulut has joined #yocto
yudjinn has joined #yocto
mbulut has quit [Ping timeout: 252 seconds]
florian_kc has quit [Ping timeout: 252 seconds]
sotaoverride is now known as Guest7770
ctraven is now known as sotaoverride
yudjinn has quit [Ping timeout: 264 seconds]
yudjinn has joined #yocto
<khem>
Guest0: well technically you can not, they are built for different OSes, but if you build it statically you have more success or perhaps build a container might be another option. Supported option would be to build for qemux86-64 and launch the image under runqemu with kvm enabled so it runs near native speed
jpuhlman has quit [Read error: Connection reset by peer]
jpuhlman- has joined #yocto
leon-anavi has quit [Quit: Leaving]
amitk_ has joined #yocto
amitk has quit [Ping timeout: 240 seconds]
florian_kc has joined #yocto
goliath has joined #yocto
<Guest0>
Thanks khem, will try that
Guest0 has quit [Quit: Client closed]
RyanEatmon has quit [Remote host closed the connection]
RyanEatmon has joined #yocto
florian_kc has quit [Ping timeout: 268 seconds]
jmd has quit [Remote host closed the connection]
mbulut has joined #yocto
vthor has quit [Ping timeout: 256 seconds]
florian_kc has joined #yocto
wdouglass has joined #yocto
<wdouglass>
when i try to do a build with SSTATE_MIRRORS set, i get an error `Exception: ModuleNotFoundError: No module named 'google'`. My sstate mirror is not in google cloud, i'm not sure why it's trying to do that. Where do i tell bitbake how to install the `google-cloud` python module?
Haxxa has quit [Quit: Haxxa flies away.]
enok has joined #yocto
Haxxa has joined #yocto
wdouglass has quit [Ping timeout: 264 seconds]
MrCryo has quit [Remote host closed the connection]
Jones42 has joined #yocto
amitk_ has quit [Ping timeout: 268 seconds]
Jones42 has quit [Remote host closed the connection]
enok has quit [Ping timeout: 264 seconds]
Kubu_work has joined #yocto
Jones42 has joined #yocto
Jones42 has quit [Ping timeout: 268 seconds]
vthor has joined #yocto
vthor has quit [Changing host]
vthor has joined #yocto
<yudjinn>
just wondering if anyone had an idea on my earlier question about libtool-native failing to build; really at a loss and I cant find anything in my searching
<absurdist>
i got some psychedelic file access permission errors using yocto on wsl2, perhaps the fs doesn't support xattr or something weird is going on
<absurdist>
should i store my yocto project on a ext4 disk image, mounted in wsl2? or is this xattr limitation of wsl2 a kernel limitation?
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<rburton>
yudjinn: pasting more of the log than that would be useful, and also saying what your usual host distro is, and what release
yudjinn has quit [Remote host closed the connection]
yudjinn has joined #yocto
yudjinn has quit [Remote host closed the connection]
<jonmason>
RP: about to update 15526 with a "works on my AMD system" and data dump my info. Anything you want me to try out?
vthor has quit [Remote host closed the connection]
<absurdist>
?Subprocess output:error: No file attributes configured??
<RP>
jonmason: just to confirm that was qemux86 with kvm for a core-image-sato ish image with testimage ?
<RP>
jonmason: /proc/cpuinfo might be helpful for comparison
<RP>
jonmason: not sure what to try yet or what the issue is :/
<jonmason>
minimal and not testimage, jsut runqemu
<jonmason>
I had to build differently than normal because I can't use kvm inside of my docker setup
<jonmason>
so no sstate....
<jonmason>
let me try it with both of those
<jonmason>
(sstate mirror wasn't working because websockets wasn't in my path....just noticed that)
Minvera has quit [Ping timeout: 255 seconds]
<RP>
jonmason: minimal doesn't seem to reproduce it as it can't "fetch" the logs from it if you're using my parselogs change
<jonmason>
building now...it'll be a little while
<RP>
jonmason: runqemu should show it but isn't how the autobuilder is doing it
vthor has joined #yocto
vthor has quit [Changing host]
vthor has joined #yocto
<jonmason>
RP: still works. testimage passed and I was able to use runqemu to get to prompt and login
<jonmason>
KVM is enabled (and was very fast)
<jonmason>
dinner now, but I can try stuff in a bit (if there are things you want me to look at)
florian_kc has quit [Ping timeout: 264 seconds]
dankm has quit [Remote host closed the connection]