reatmon_ has quit [Remote host closed the connection]
reatmon_ has joined #yocto
ablu has quit [Ping timeout: 260 seconds]
ehussain has quit [Ping timeout: 276 seconds]
ehussain has joined #yocto
ehussain has quit [Ping timeout: 255 seconds]
rbox has quit [Ping timeout: 252 seconds]
rbox has joined #yocto
jclsn has quit [Ping timeout: 276 seconds]
jclsn has joined #yocto
amitk has joined #yocto
heidaren has quit [Remote host closed the connection]
heidaren has joined #yocto
Minvera has quit [Ping timeout: 255 seconds]
vthor has quit [Remote host closed the connection]
vthor has joined #yocto
vthor has quit [Changing host]
vthor has joined #yocto
jmd has joined #yocto
ablu has joined #yocto
jmd has quit [Remote host closed the connection]
pbiel has joined #yocto
Guest12 has joined #yocto
<Guest12>
Hello, I have a question regarding the default Yocto Linux kernel configuration. I noticed that the systemtap.scc fragment is included in the standard.scc kernel fragment, which in turn enables CONFIG_DEBUG_INFO in the kernel configuration. This setting significantly increases the size of kernel modules and prolongs build times. Could you please
<Guest12>
explain the rationale behind including systemtap.scc in the default configuration?
alessioigor has joined #yocto
<jdiez>
hi folks. I'm running into a strange error, saying that no SPDX file can be found for `initscripts`. This is on unmodified poky scarthgap, but I had previously built kirkstone in this build directory. The actual error:
<jdiez>
ERROR: run-postinsts-1.0-r0 do_create_spdx: Cannot find any SPDX file for recipe initscripts, False sstate:initscripts:core2-64-poky-linux:1.0:r0:core2-64:12: sstate:initscripts::1.0:r0::12:
<jdiez>
the strange thing is that I'm not even building for core2-64-poky-linux (aka qemux86-64), but I did that earlier. I also tried `bitbake -c cleanall initscripts`, but that didn't help. Any clues?
CrazyGecko has joined #yocto
goliath has joined #yocto
rob_w has joined #yocto
xmn has quit [Ping timeout: 245 seconds]
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #yocto
rfuentess has joined #yocto
mckoan|away is now known as mckoan
florian has joined #yocto
ray-san has joined #yocto
luc4 has joined #yocto
leon-anavi has joined #yocto
<luc4>
Hello! Is there a guide somewhere on how to add pulseaudio to a Yocto system?
<mckoan>
luc4: no, and may be not so easy. Add to your image pulseaudio-server.
<mckoan>
luc4: however we have a quite good experience with that
Guest12 has quit [Ping timeout: 256 seconds]
<luc4>
mckoan: thanks! Do I also have to start the server manually?
<mckoan>
luc4: you can create your SystemV or systemd service
<ray-san>
i try to build nodejs. if i tell bitbake to compile on 32 CPUs, it fails reliable every time. if i reduce the build to 16 cores, it suceeds. thats kinda odd. anyone here experienced similar behaviour?
florian has quit [Ping timeout: 260 seconds]
<ray-san>
ah, maybe my compiler gets OOM nuked, i guess this may be an issue :D
<mckoan>
ray-san: it is a known broblem with nodejs. You have to reduce core numbers
<ray-san>
mckoan: i guess, increasing available RAM also helps?
<mckoan>
ray-san: usually not
<mckoan>
ray-san: see BB_NUMBER_THREADS and PARALLEL_MAKE
<ray-san>
odd...ok than move on with just 16 cores, i got time :P
<RP>
ray-san: if you're running out of memory ram will help. You could just dial down PARALLEL_MAKE for the nodejs recipe
mvlad has joined #yocto
<ray-san>
RP: ah you can overwrite this variable in a recipe, didn't know that
<RP>
rburton: that spdx/testsdk patch doesn't work, it breaks buildtools for reasons I don't understand :(
<RP>
ah, I do understand now :/
<landgraf>
mckoan: in codebuild env nodejs compilation crashes with OOM on 8vCPU/16GBs instance, I had to switch to 36/70 one if nodejs updated and it works reliably.
<landgraf>
setting of BB_NUMBER_THREADS for nodejs causes codebuild timeout :-/
mbulut has joined #yocto
<mckoan>
landgraf: thx
<JaMa>
landgraf: set P_M for nodejs to less then number of cores if you don't have 2GB RAM per core
pbiel has quit [Remote host closed the connection]
pbiel has joined #yocto
<mcfrisk>
2 GB of physical RAM per core is quite often required to build complex SW stacks
<mcfrisk>
per CPU thread, not core
rob_w has quit [Remote host closed the connection]
<luc4>
Hello! I created an image including pulseaudio. I tried to start it with "sudo systemctl --user start pulseaudio" but I'm getting "Failed to connect to bus: No medium found". Any idea why? Is it talking about dbus?
<landgraf>
yes, it is
<rburton>
luc4: if your app/environment/whatever runs as a non-root user then that user can start a pulseaudio daemon. upstream recommend user daemon, not system-wide daemons.
<luc4>
rburton: If I try to run it as a user I get this horrible log: "W: [pulseaudio] pid.c: Stale PID file, overwriting.\n*** stack smashing detected ***: terminated\n*** stack smashing detected ***: terminated".
<luc4>
rburton: however yes, my app runs as a user
landgraf has quit [Quit: WeeChat 3.6]
landgraf has joined #yocto
landgraf has quit [Client Quit]
<luc4>
oh... should I configure /etc/pulse/client.conf first maybe?
landgraf has joined #yocto
florian has joined #yocto
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
florian_kc has joined #yocto
florian has quit [Ping timeout: 276 seconds]
florian__ has joined #yocto
florian_kc has quit [Read error: Connection reset by peer]
florian has joined #yocto
Guest13 has joined #yocto
<Guest13>
how do i add an environment variable to a recipe?
<Guest13>
can i do it on the recipe side instead of bbclass?
florian__ has quit [Ping timeout: 252 seconds]
Guest13 has quit [Quit: Client closed]
luc4 has quit [Quit: Konversation terminated!]
luc4 has joined #yocto
<rburton>
Guest1147: export FOO=bar in the recipe
<rburton>
RP: the cve 'database malformed' problems, have you only seen those in oe-selftest or other jobs too?
<RP>
rburton: only selftest
<rburton>
that's interesting
<rburton>
parallel fetches, maybe?
<RP>
rburton: I'm wondering about some kind of race, yes
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
MrCryo has joined #yocto
heidaren has quit [Quit: Bye ~]
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
Minvera has joined #yocto
Minvera has quit [Read error: Connection reset by peer]
<luc4>
Hello! I'm getting a crash in pulseaudio. Is it possible that alsa-lib is built using 64bit time structures while pulseaudio is not? According to the build logs this seems to be the case, but I cannot find confirmation in the bb files.
alessioigor has quit [Remote host closed the connection]
mk3890 has joined #yocto
<rburton>
luc4: that would be unfortunate if so. what release?
<JaMa>
Failed to connect to code.qt.io port 443: Connection timed out
<JaMa>
WARNING: The free space of /tmp (/dev/mapper/debian11--ty--1--vg-tmp) is running low (0.000GB left)
<halstead>
I can fix one of these.
<JaMa>
no rush (just becaue of webOS OSE builds) but if it's breaking other builds as well than yes please
<JaMa>
I was just wondering if there are some other webOS builds, because rburton just sent e-mail that it did build last week and will do another this weekend (while it was triggered 14 hours ago)
<rburton>
JaMa: there was one last week that actually passed (once it got a rekick)
<JaMa>
I see only the one from 2 weeks ago
alessioigor has joined #yocto
<JaMa>
then failed due to code.qt.io 7 days ago and due to disk space from 15 hours ago
leon-anavi has quit [Quit: Leaving]
florian has quit [Ping timeout: 252 seconds]
alessioigor has quit [Remote host closed the connection]
florian has joined #yocto
florian has quit [Ping timeout: 260 seconds]
enok has joined #yocto
<vmeson>
halstead: Nrpt would like a bugzilla account.