<vmeson>
jaskij[m]: what patch do you mean? This one? meta/recipes-devtools/gcc/gcc/0028-debug-101473-apply-debug-prefix-maps-before-checksum.patch (was renamed slightly.)
<jaskij[m]>
The TLDR is that I want to submit a new recipe, and it defaults to `-O2 -flto -ftree-loop-vectorize` and I'm not sure what to do about it. Definitely dropping `-O2`, `-ftree-loop-vectorize` can stay, I think, not sure about `-flto`
<vmeson>
jaskij[m]: I susepct you mean this thread: [OE-core] [master][PATCH 0/4] Reproducible LTO builds
* vmeson
check to see if anything was merged...
<vmeson>
d1fd369341 lto.inc: disable LTO for grub <-- seems to be it or part of it.
jclsn has joined #yocto
<jaskij[m]>
vmeson: that looks about right, thanks. Although I approached this from a wrong direction - I care about which flags to leave in the recipe I'm writing. I suspect `-flto` would be connected to this.
<vmeson>
oe-core does require that builds are reproducible
<vmeson>
I'd send the patch and point out that reproducibility might be a concern and ask for advice.
<jaskij[m]>
that's what I'll do then
<vmeson>
jaskij[m]: cool. back to weekending...
<jaskij[m]>
now I'm having doubts whether it's not an unnecessary thing - it's `btop`, basically a better-looking `htop`, with some expanded capabilities
<jaskij[m]>
eh, I'll submit and worst case it will be rejected
<vmeson>
ah, yes. performance probably isn't critical for such an application, is it?
<jaskij[m]>
ayup, although the author is adamant on keeping it as high as possible
<vmeson>
ah, I see. Send it in and we'll see. It'll likely go into meta-openembedded right?
<jaskij[m]>
(seeing as this program has been through two rewrites - originally written in bash, rewritten in Python, then in C++)
<jaskij[m]>
and yup, I'd be submitting it to meta-oe if anywhere, just besides the existing htop recipe
<vmeson>
jaskij[m]: they'll make it to Rust eventually! ;-)
jclsn has quit [Ping timeout: 248 seconds]
<jaskij[m]>
there actually is an issue for RiiR :P not happening, but I think someone else got on that
<jaskij[m]>
I myself considered doing it as an exercise, after the boring stuff I had to write at work recently
<jaskij[m]>
actually, I need to figure out how to submit some stuff I did for work... boss probably won't agree, and me doing a clean rewrite probably would be skirting the copyrights a bit much
<jaskij[m]>
Turns out you can quite easily write a Python script to mock enough of `pg_config` to build PostgreSQL extensions
<vmeson>
RiiR ?
jclsn has joined #yocto
<vmeson>
RIIR: rewrite it in rust
jclsn has quit [Ping timeout: 246 seconds]
jclsn has joined #yocto
jclsn has quit [Ping timeout: 276 seconds]
<seninha>
ping
jclsn has joined #yocto
jclsn has quit [Ping timeout: 240 seconds]
jclsn has joined #yocto
jclsn has quit [Ping timeout: 240 seconds]
jclsn has joined #yocto
jclsn has quit [Ping timeout: 250 seconds]
kanavin has quit [Ping timeout: 260 seconds]
jclsn has joined #yocto
seninha has quit [Ping timeout: 276 seconds]
jclsn has quit [Ping timeout: 246 seconds]
seninha has joined #yocto
jclsn has joined #yocto
jclsn has quit [Ping timeout: 276 seconds]
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
jclsn has joined #yocto
jclsn has quit [Ping timeout: 248 seconds]
jclsn has joined #yocto
sakoman has joined #yocto
jclsn has quit [Ping timeout: 256 seconds]
jclsn has joined #yocto
jclsn has quit [Ping timeout: 256 seconds]
jclsn has joined #yocto
mrnuke has quit [Ping timeout: 248 seconds]
fray has quit [Ping timeout: 248 seconds]
jclsn has quit [Ping timeout: 276 seconds]
jclsn has joined #yocto
mrnuke has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
sakoman has quit [Quit: Leaving.]
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
xantoz has quit [Ping timeout: 245 seconds]
mrnuke has quit [Ping timeout: 260 seconds]
nemik has quit [Ping timeout: 276 seconds]
mrnuke has joined #yocto
nemik has joined #yocto
mrnuke has quit [Ping timeout: 260 seconds]
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
Wouter0100 has quit [Remote host closed the connection]
Wouter0100 has joined #yocto
mrnuke has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
<seninha>
Hi, I'm getting this error while compiling ovmf-native: https://ttm.sh/blH.txt
<seninha>
nvm, I manually applied a patch that fixed those errors
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
Habbie has quit [Ping timeout: 240 seconds]
florian_kc has joined #yocto
Habbie has joined #yocto
seninha has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
oberonc has joined #yocto
<oberonc>
how do I add dhcpd capabilities to an image ? which recipe is relevant ?
ilunev has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
<dwagenk>
<oberonc> "how do I add dhcpd capabilities..." <- depends on the tool you want to use. if your image includes systemd you could add `systemd-networkd` (+ your custom network config files). `dnsmasq` is also an option (should be in meta-openembedded/meta-networking). I think busybox also has a separate dhcp-server package (`busybox-udhcpd`)
<oberonc>
systemd-networkd isnt only a dhcp client ?
<oberonc>
(I do use systemd)
<dwagenk>
go with whatever tool fits into your image/distro best or which tools config file structure you prefer...
<dwagenk>
oberonc: i think it can be configured to also be a server
<oberonc>
when I add "kea" to RDEPENDS it doesnt enable the service file by default so the image boots without starting kea
barometz has quit [Ping timeout: 256 seconds]
fray has joined #yocto
<Saur[m]>
oberonc: Seems about right as the recipe does `SYSTEMD_AUTO_ENABLE = "disable"`. Why that is, I don't know. It has been there since the recipe was added to meta-networking, so no explanation in the Git log.
<oberonc>
if I add the line SYSTEMD_AUTO_ENABLE = "enabled" to a .bbappend file it will be fixed ?
<Saur[m]>
It should be "enable", but except for that it should work. Try it.