<mcfrisk_>
Guest66: yocto build system builds all recipes (== SW components) with debug flags (-g) to collect debug symbols for later use. The debug symbols get automatically stripped to -dbg binary packages which can be used in SDK etc to decode back traces from core dumps, installed to target to work with gdb etc. This QA check noticed that nodejs binary did not include any debug symbols when it should have. The
<mcfrisk_>
QA check can be disabled in the recipe, or if you care about the debug symbols, then fix nodejs recipe to compile the binary with -g which is in the default bitbake CFLAGS/CXXFLAGS
florian has joined #yocto
<Guest66>
mcfrisk_ could you please tell me how can I disable QA check
<Guest66>
landgraf mcfrisk should I then add in nodejs recipe CXXFLAGS=-g and CFLAGS=-g
<mcfrisk_>
Guest66: that would overwrite the flags and break cross compilation. Rather, check why nodejs is overwriting the defaults inside nodejs side config and build scripts
enok has joined #yocto
<Guest66>
that would be tough for me I try
rfuentess has joined #yocto
Kubu_work has joined #yocto
<mcfrisk_>
Guest66: without debug symbols you will not be able to decode crashes/core dumps or debug nodejs
zpfvo has joined #yocto
mckoan|away is now known as mckoan
<landgraf>
Guest66: nodejs_20.12.2.bb works fine in our env without insane_skip
enok has quit [Ping timeout: 252 seconds]
frieder has joined #yocto
mvlad has joined #yocto
alperak has joined #yocto
Guest66 has quit [Quit: Client closed]
xmn has joined #yocto
frieder has quit [Ping timeout: 252 seconds]
leon-anavi has joined #yocto
prabhakalad has joined #yocto
Tyaku has joined #yocto
frieder has joined #yocto
Tyaku has quit [Quit: leaving]
Guest66 has joined #yocto
xmn has quit [Ping timeout: 265 seconds]
<Guest66>
mcfrisk_ for me as a beginner it's bit hard to find out, what make nodejs overwrites flags. As I am also not familiar with debug tools, which I can use to find out
<Guest66>
landgraf we can't use nodejs_20 for our application
Guest66 has quit [Quit: Client closed]
<mcfrisk_>
Guest66: using yocto means you create your own custom Linux distro. It is hard work with a lot of compromises. In the end you maintain all of it, including nodejs. Sometimes it would be better for users to take general purpose Linux distros like Debian. If applications etc dictate SW component revisions without maintenance or upstream aspects even considered, then I think at some point the house of cards
<mcfrisk_>
will fall badly.
Guest66 has joined #yocto
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #yocto
sakoman has quit [Read error: Connection reset by peer]
sakoman has joined #yocto
tlwoerner has quit [Quit: Leaving]
sakoman has quit [Ping timeout: 255 seconds]
Perflosopher has quit [Read error: Connection reset by peer]
frieder has quit [Remote host closed the connection]
sotaoverride has quit [Ping timeout: 246 seconds]
frieder has joined #yocto
sotaoverride has joined #yocto
vthor has quit [Ping timeout: 252 seconds]
goliath has quit [Quit: SIGSEGV]
pbsds3 has quit [Ping timeout: 248 seconds]
pbsds3 has joined #yocto
sotaoverride has quit [Ping timeout: 248 seconds]
reatmon_ has quit [Remote host closed the connection]
reatmon_ has joined #yocto
MarioMariollini has joined #yocto
<MarioMariollini>
Hi guys. I am trying to ship one of u-boot's tools into my sdk (relocate-rela). I need to compile this under the target architecture toolchain (aarch64), but for x86. This part is fine, I get an x86 binary. The problem is I don't know how to put it into the sdk files instead of the arm image. I am getting now an error at do_package because
<MarioMariollini>
aarch64-oe-linux-objcopy doesn't recognize the architecture.
<MarioMariollini>
How would I change the do_package for this to work?
<DixitP>
I am trying to emulate battery device in the QEMU x86-64. I am building QEMU images using Yocto reference distribution poky, I am building core-image-sato image for the qemux86-64 machine. My goal is to see battery icon in to the QEMU GUI.
<DixitP>
As per my understanding, Battery device communicates using acpi so the target needs to have acpi support. I have modified qemux86-64 machine file to have acpi as MACHINE_FEATURES. Now the QEMU needs to have an emulated/fake battery device which can populate the battety device and its information so it can be visible as icon in to the GUI. From
<DixitP>
exploration I found that below commands (-device option) emulates battery device, But I don't see any battery device in the GUI with these.