<MastaG>
Quick question, I'm building using bitbake 2.10 and openembedded styhead, but I'm having trouble building native packages, such as "util-linux-native":
<MastaG>
./util-linux-2.40.2/misc-utils/lsfd-sock-xinfo.c:31:10: fatal error: linux/sock_diag.h: No such file or directory
<rburton>
MastaG: your host distro is missing the libc/kernel headers
<rburton>
on debian, linux-libc-dev though how you have a working compiler without those is a good question
<MastaG>
@rburton that's the thing, I have everything installed and the file exists.
<MastaG>
$ rpm -qf /usr/include/linux/sock_diag.h
<MastaG>
kernel-headers-6.11.3-200.fc40.x86_6
<MastaG>
I'm running Fedora 40 btw
<MastaG>
according to the documentation, openembedded seems to use the host toolchain for building native things
<rburton>
yes
<rburton>
hard to build a toolchain without a toolchain :)
<rburton>
MastaG: grab poky, checkout the styhead branch, and try a bitbake util-linux-native in that with _no_ changes
<MastaG>
alright
Ad0 has quit [Ping timeout: 252 seconds]
olani has quit [Remote host closed the connection]
<MastaG>
This is with MACHINE=genericx86-64 and DISTRO=poky, I've excluded my own layers
<rburton>
i'd like to see it with actual poky and styhead to rule out any differences between your setup and what the autobuilder tests regularly on f40
<MastaG>
What is poky? I've added meta-yocto/meta-poky and meta-yocto/meta-yocto-bsp to my layers and removed my own layers
<MastaG>
had some locate compiler version.. probably for some leftover project
<MastaG>
*local
Daanct12 has quit [Quit: WeeChat 4.4.3]
MastaG has quit [Ping timeout: 256 seconds]
florian_kc has quit [Ping timeout: 248 seconds]
cyxae has joined #yocto
gspbirel56 has quit [Ping timeout: 260 seconds]
steelswords94 has joined #yocto
florian has quit [Quit: Ex-Chat]
Tyaku has joined #yocto
Grogu68 has joined #yocto
<Grogu68>
My second yocto question: How do you recommend learning how to use yocto? How to develop/configure a build for it. I've read some of the docs from the yocto project. They read like "Handbook for the Recently Deceased" from Beetlejuice ... they suck ... like most documentation (other than for IKEA furniture)
<rburton>
Grogu68: Embedded Linux Development Using The Yocto Project isn't a bad book
halloy4475 has joined #yocto
halloy4475 has quit [Remote host closed the connection]
davidinux1 has joined #yocto
<mckoan>
Grogu68: my favourite is Embedded Linux Systems with the Yocto Project by Rudolf Streif
<Tyaku>
informations when I read the DTS from /proc/device-tree/xxxxx directories. The problem is that i don't really know what to check. The memfree in /proc/meminfo seems to be good enought
<Tyaku>
Also I suspect something missconfigured because when a software is leaking, the OOM killer kill it. But now NOTHING is killed by OOM
<Tyaku>
When My kernel starts I have this log: 'Memory: 226788K/393216K available' at this point it seems correct: I have 128MBytes reserved for OPTEE stuff and 384MBytes (393216K) for the Linux. In these 384MBytes I have 128MBytes of CMA.
zpfvo has quit [Remote host closed the connection]
pidge has joined #yocto
pidge_ has joined #yocto
pidge has quit [Read error: Connection reset by peer]
pidge_ has quit [Ping timeout: 272 seconds]
pidge has joined #yocto
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #yocto
florian has quit [Ping timeout: 276 seconds]
leon-anavi has quit [Quit: Leaving]
benkard has joined #yocto
mulk has quit [Ping timeout: 272 seconds]
benkard is now known as mulk
Grogu68 has quit [Ping timeout: 256 seconds]
RobW has joined #yocto
RobW has quit [Ping timeout: 256 seconds]
tyzef has joined #yocto
Guest18 has joined #yocto
<Guest18>
hey!! in local.conf can I set a task flag for a specific recipe? such as do_rootfs[noexec]:core-image-minimal = "1"
florian has joined #yocto
<Guest18>
or any other way do override that task to do nothing, or any way to build all the dependencies but without actually constructing the rootfs?
<Guest18>
thank you
tyzef has quit [Quit: WeeChat 3.8]
<rburton>
Guest18: what are you actually trying to do? running rootfs but not actually run it seems like a weird thing to want to do.
<Guest18>
I would like just to construct the cache for a particular image, but without spending the time on creating the image itself
<Guest18>
so I would like just to build all the dependencies, but not the actual image
druppy has joined #yocto
<rburton>
the time to build the rootfs is pretty minimal compared to the rest, so if you just ask it to do up to rootfs then it won't bother building images but would have actually pulled in everything in the image
<rburton>
bitbake myimage -c rootfs
Guest18 has quit [Quit: Client closed]
ptatrai has quit [Remote host closed the connection]
ptatrai has joined #yocto
prabhakalad has quit [Ping timeout: 260 seconds]
druppy has quit [Ping timeout: 255 seconds]
prabhakalad has joined #yocto
ptatrai has quit [Ping timeout: 252 seconds]
ptatrai has joined #yocto
reatmon_ has quit [Remote host closed the connection]
reatmon_ has joined #yocto
ptatrai has quit [Ping timeout: 260 seconds]
davidinux1 has joined #yocto
cyxae has quit [Quit: cyxae]
xmn has quit [Read error: Connection reset by peer]