theJoker8814 is now known as Guest214
thejoker8814 has joined #openwrt-devel
Guest214 has quit [Ping timeout: 480 seconds]
Emantor has quit [Quit: ZNC - http://znc.in]
Emantor has joined #openwrt-devel
<schmars[m]> about xz and PKG_MIRROR_HASH - for a custom package of mine, the snapshot docker.io/openwrt/sdk container complains about a mismatch, the tarballed sdk from downloads.openwrt.org doesn't complain
<mirko> mrnuke: what was the reason not to include it as base pkg?
<mirko> i have a question re sda switch config - is it expected that [1] is working but [2] isn't? At least that's the case for my gs1900 switch right now. mind the vlan id
<mrnuke> mirko: I don't remember the full discussion.
<mrnuke> Someone suggested adding it as a feeds package. hurricos and I then set up the realtek-poe repo to allow this use case, and we
<mrnuke> and we hit <Enter> too early. I need to stop typing when it's this late at night :p
goliath has quit [Quit: SIGSEGV]
tSYS has quit [Quit: *squeak*]
skynet2 has quit [Ping timeout: 480 seconds]
tSYS has joined #openwrt-devel
minimal has quit [Quit: Leaving]
<Mangix> schmars[m]: yep. this is temporary until the zstd transition is done.
Slimey has quit [Read error: No route to host]
Slimey has joined #openwrt-devel
rua has quit [Quit: Leaving.]
rz has quit [Ping timeout: 480 seconds]
rz has joined #openwrt-devel
<KGB-2> https://tests.reproducible-builds.org/openwrt/openwrt_ath79.html has been updated. (98.7% images and 100.0% packages reproducible in our current test framework.)
rz has quit [Ping timeout: 480 seconds]
_lore_ has quit [Ping timeout: 480 seconds]
robimarko has joined #openwrt-devel
<f00b4r0> robimarko: congrats for your hard work! Let's ship it :)
<robimarko> f00b4r0: Just did it, lets see what breaks :)
<f00b4r0> yay! :)
<robimarko> Probably a good idea to refresh the default feed hashes
<f00b4r0> #14619 should be a walk in the park in comparison
<robimarko> Making git clones reproducible was a major pain
<robimarko> Ansuel did his magic on that
<f00b4r0> yeah I think we probably want to announce on m-l/wiki that we're switching away from xz so that packages maintainers know what to expect
<f00b4r0> yeah that was really cool
<f00b4r0> i'll test #14619 on top of current master to make sure nothing broke there
<robimarko> that would be great
<f00b4r0> let's make use of all these idle cpu cores :)
<stintel> yay, eth0 link up on EAP683-LR, no traffic though
<stintel> and no GPL dump on the TP-Link website
<f00b4r0> robimarko: from a clean master checkout, I git am'd 14619, fetched config.buildinfo from x86/64, ran make defconfig and just fired make -j`nproc`
<f00b4r0> i didn't bother with feeds to make the test a bit speedier since feeds are orthogonal to the changes tested
<robimarko> Yeah, I ignored the feeds for this PR as well
<f00b4r0> this should essentially reproduce a buildbot image build
<f00b4r0> result expected in ~50mn
<owrt-images-builds> Build [#147](https://buildbot.openwrt.org/images/#/builders/124/builds/147) of `master_bcm27xx/bcm2710` completed successfully.
<f00b4r0> we'll get some numbers on memory usage as well, which'll be interesting
<robimarko> packaging repos is much faster
<f00b4r0> gdb and binutils failed to build. /me checks
<f00b4r0> compress.c:24:10: fatal error: zstd.h: No such file or directory
<f00b4r0> that's in gdb-14.1/bfd
<robimarko> Ugh, I just built the whole toolchain
<f00b4r0> no zstd.h in staging_dir/host/include
<robimarko> Hm, so it could be getting header from my host then?
<f00b4r0> quite likely
<f00b4r0> I don't have libzstd-dev installed
<robimarko> Ugh, indeed header is not getting installed
<robimarko> Yeah, install-includes is not called
<robimarko> Yeah, just testing it out
<f00b4r0> lemme know when I should pull and restart test
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/178/builds/148) of `master_sifiveu/generic` failed.
<f00b4r0> don't bother looking, it's the same thing
<robimarko> f00b4r0: fix pushed
<f00b4r0> btw we didn't document why we use install-pc install-static
* f00b4r0 pulls
<robimarko> Because if just install was used then shared library would be installed as well
<f00b4r0> gdb builds
<f00b4r0> it seems gcc is still using xz, I caught an xzcat something on top
<robimarko> GCC is still fetched as XZ
<f00b4r0> one thing at a time i guess :)
<robimarko> I just love how people start commenting on merged changes while they had 0 comments on a PR that has been open for a long time
<f00b4r0> just ignore them :P
<owrt-images-builds> Build [#152](https://buildbot.openwrt.org/images/#/builders/58/builds/152) of `master_ipq40xx/generic` failed.
<f00b4r0> also zstd takes a few seconds to build, this is completely irrelevant
<f00b4r0> just ignore the noise
<owrt-images-builds> Build [#144](https://buildbot.openwrt.org/images/#/builders/137/builds/144) of `master_x86/legacy` failed.
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/145/builds/148) of `master_octeon/generic` failed.
<f00b4r0> toolchain built
<robimarko> Buildbots were fast, they caught the commit before zstd was fixed
<f00b4r0> probably a couple bots ended their run at the time you pushed
<f00b4r0> good thing it's caturday and nobody's paying attention ;D
<robimarko> Yeah, unlucky timing
<robimarko> Do I not understand english or?
<f00b4r0> building target/linux atm. I'm quite ahead of the bots so we should be able to catch any remaining nasties
<robimarko> ZSTD readme clearly states that Make is the only official build system
<f00b4r0> robimarko: just ignore the guy
<f00b4r0> it's falling on deaf ears
<robimarko> Yeah
<robimarko> BTW, I should really make some minimal docker image without anything other than minimal prereq to build stuff
<f00b4r0> yeah; i've been thinking exactly the same
<f00b4r0> though I keep my buildbox very lean for that reason
<robimarko> Cause even minimal Alpine wasnt enough since it has zstd
<f00b4r0> i'll try to time make tools/zstd/compile in buildbot conditions if other make silly comments about which build scheme we're using.
<f00b4r0> target built
<f00b4r0> it's almost over
<robimarko> That PR should work as its just changing the compression for IB and SDK
<f00b4r0> yep
<f00b4r0> but it's using --ultra -20, the important info will be mem usage I think
<robimarko> We are currently using --ultra -20 for all packaging
<f00b4r0> true. But IB/SDK aren't exactly small :)
<\x> ximi shipping 1GB ram on these
<f00b4r0> ah fsck
<f00b4r0> xdp-tools still fails to build
<f00b4r0> it's been failing for me forever
<robimarko> Yeah, that thing has been broken
<f00b4r0> how come it builds on buildbots though
<robimarko> I think there is a huge PR trying to fix it
<robimarko> Basically I think its picking up stuff from the host
<f00b4r0> ugh
<robimarko> OMG, we have package that is being fetched from SVN
<f00b4r0> lol
* f00b4r0 disables xdp, restarts build
<robimarko> make package/download failed and it turns out I dont have subversion client at all
<owrt-images-builds> Build [#156](https://buildbot.openwrt.org/images/#/builders/15/builds/156) of `master_mxs/generic` failed.
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/126/builds/149) of `master_tegra/generic` failed.
<owrt-images-builds> Build [#153](https://buildbot.openwrt.org/images/#/builders/60/builds/153) of `master_realtek/rtl839x` failed.
<robimarko> All builds will fail as they just managed to pick the same commit
<owrt-images-builds> Build [#147](https://buildbot.openwrt.org/images/#/builders/205/builds/147) of `master_mpc85xx/p1020` failed.
<f00b4r0> yep
<f00b4r0> let's pretend it never happened :)
<robimarko> Luckily its early in the process
<robimarko> So they will move on quickly
<f00b4r0> *nod*
<f00b4r0> and luckily we caught it before the first failures so the next run will be good
<f00b4r0> package/install finishing here
<f00b4r0> doing sdk/install I saw a few calls to xz in top
<f00b4r0> we might have some leftover cruft
<f00b4r0> zstd topped out at 2.7G use
<f00b4r0> and done
<f00b4r0> all good!
<stintel> \o/
<f00b4r0> robimarko: for the record: time make -j8 tools/zstd/compile real 0m32.589s
<f00b4r0> anyone who gives you shit about using make, just tell them that ;P
<f00b4r0> (cpu is old - E5-2697 v2)
<f00b4r0> and time given icludes libdeflate build
<robimarko> libdeflate is extremely quick
<robimarko> zstd as well
<f00b4r0> yep
<stintel> ah this EAP683-LR is not playing along :(
<stintel> tried both mac@0 and mac@1 but no traffic in either direction afaict
<robimarko> stintel: TP-Link has an GPL email that you can request sources for devices that dont have them listed
<stintel> already done ;)
<owrt-images-builds> Build [#167](https://buildbot.openwrt.org/images/#/builders/8/builds/167) of `master_oxnas/ox820` failed.
<f00b4r0> robimarko: so I see why there was xz calls: toolchain is still packaged as xz
<robimarko> f00b4r0: nice catch
<owrt-images-builds> Build [#147](https://buildbot.openwrt.org/images/#/builders/110/builds/147) of `master_zynq/generic` failed.
KGB-2 has quit [Remote host closed the connection]
<owrt-images-builds> Build [#152](https://buildbot.openwrt.org/images/#/builders/97/builds/152) of `master_ixp4xx/generic` failed.
<f00b4r0> llvm is also packaged as xz
<f00b4r0> these were the only two hits found in find bin -iname '*.xz'
KGB-2 has joined #openwrt-devel
<f00b4r0> fwiw, list of sources packaged as xz from buildbot config build (without pulling feeds): https://pastebin.com/4ATkBzbs
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/138/builds/150) of `master_bcm27xx/bcm2708` failed.
<owrt-images-builds> Build [#152](https://buildbot.openwrt.org/images/#/builders/19/builds/152) of `master_apm821xx/nand` failed.
<robimarko> Ok, now buildbots are failling on cp: cannot stat '/builder/shared-workdir/build/build_dir/toolchain-arm_arm1176jzf-s+vfp_gcc-13.2.0_musl_eabi/gdb-14.1/gdb/data-directory/python': No such file or directory
<f00b4r0> sounds like disk full
<f00b4r0> not
<f00b4r0> ls: cannot access 'build_dir/toolchain-x86_64_gcc-13.2.0_musl/gdb-14.1/gdb/data-directory/python': No such file or directory
<f00b4r0> that didn't fail the build though
<f00b4r0> i have a 'stamp-python' in that folder
<robimarko> One more thing that doesnt fail locally
<owrt-images-builds> Build [#152](https://buildbot.openwrt.org/images/#/builders/51/builds/152) of `master_ramips/rt3883` failed.
<owrt-images-builds> Build [#147](https://buildbot.openwrt.org/images/#/builders/185/builds/147) of `master_ipq806x/generic` failed.
<f00b4r0> i have to admit I can't make sense of that one
<f00b4r0> i don't see how it could be remotely related to your changes
<owrt-images-builds> Build [#147](https://buildbot.openwrt.org/images/#/builders/204/builds/147) of `master_sunxi/cortexa53` failed.
<f00b4r0> I think it's unrelated but I think I've found the bug
<f00b4r0> ifneq ($(CONFIG_GDB_PYTHON),)
<robimarko> But its been like that for 3 years
<f00b4r0> # CONFIG_GDB_PYTHON is not set
<f00b4r0> wanna bet python was indirectly pulled in by something else through xz?
<f00b4r0> so the makefile is broken and that's why it fails
<f00b4r0> have to run now, feel free to try a patch if you have time :)
<f00b4r0> bbl
<owrt-images-builds> Build [#143](https://buildbot.openwrt.org/images/#/builders/149/builds/143) of `master_mediatek/filogic` failed.
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/63/builds/150) of `master_lantiq/xway` failed.
<owrt-images-builds> Build [#142](https://buildbot.openwrt.org/images/#/builders/219/builds/142) of `master_ath79/generic` failed.
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/234/builds/148) of `master_ipq40xx/mikrotik` failed.
<owrt-images-builds> Build [#145](https://buildbot.openwrt.org/images/#/builders/115/builds/145) of `master_x86/64` failed.
<robimarko> Gotta run now, will fixup in the evening
<owrt-images-builds> Build [#145](https://buildbot.openwrt.org/images/#/builders/210/builds/145) of `master_rockchip/armv8` failed.
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/142/builds/148) of `master_bcm27xx/bcm2711` failed.
robimarko has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/220/builds/149) of `master_mpc85xx/p2020` failed.
vincejv has quit [Ping timeout: 480 seconds]
<owrt-images-builds> Build [#172](https://buildbot.openwrt.org/images/#/builders/1/builds/172) of `master_ipq40xx/chromium` failed.
goliath has joined #openwrt-devel
<owrt-images-builds> Build [#156](https://buildbot.openwrt.org/images/#/builders/9/builds/156) of `master_pistachio/generic` failed.
<owrt-images-builds> Build [#145](https://buildbot.openwrt.org/images/#/builders/189/builds/145) of `master_mediatek/mt7622` failed.
<owrt-images-builds> Build [#147](https://buildbot.openwrt.org/images/#/builders/61/builds/147) of `master_ramips/mt7621` failed.
<owrt-images-builds> Build [#105](https://buildbot.openwrt.org/images/#/builders/237/builds/105) of `master_bcm27xx/bcm2712` failed.
<owrt-images-builds> Build [#153](https://buildbot.openwrt.org/images/#/builders/99/builds/153) of `master_bcm4908/generic` failed.
<owrt-images-builds> Build [#153](https://buildbot.openwrt.org/images/#/builders/173/builds/153) of `master_lantiq/ase` failed.
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/187/builds/149) of `master_lantiq/xway_legacy` failed.
<owrt-images-builds> Build [#153](https://buildbot.openwrt.org/images/#/builders/78/builds/153) of `master_ramips/rt305x` failed.
<owrt-images-builds> Build [#153](https://buildbot.openwrt.org/images/#/builders/85/builds/153) of `master_bcm53xx/generic` failed.
<owrt-images-builds> Build [#146](https://buildbot.openwrt.org/images/#/builders/38/builds/146) of `master_x86/generic` failed.
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/45/builds/149) of `master_sunxi/cortexa7` failed.
dannyAAM has quit [Quit: znc.saru.moe : ZNC 1.6.2 - http://znc.in]
<owrt-images-builds> Build [#155](https://buildbot.openwrt.org/images/#/builders/25/builds/155) of `master_realtek/rtl838x` failed.
<owrt-images-builds> Build [#14](https://buildbot.openwrt.org/images/#/builders/240/builds/14) of `master_imx/cortexa53` failed.
dannyAAM has joined #openwrt-devel
dannyAAM has quit []
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/162/builds/150) of `master_bmips/bcm6358` failed.
<f00b4r0> so looking again, the 'cp' is prefixed with '-' so it shouldn't fail
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/206/builds/149) of `master_bcm47xx/legacy` failed.
dannyAAM has joined #openwrt-devel
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/68/builds/150) of `master_octeontx/generic` failed.
<f00b4r0> ha, the error is actually higher up in the log
<owrt-images-builds> Build [#146](https://buildbot.openwrt.org/images/#/builders/157/builds/146) of `master_mvebu/cortexa72` failed.
<owrt-images-builds> Build [#43](https://buildbot.openwrt.org/images/#/builders/239/builds/43) of `master_starfive/generic` failed.
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/94/builds/150) of `master_ipq806x/chromium` failed.
<f00b4r0> phtread symbols not found
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/148/builds/148) of `master_bcm27xx/bcm2709` failed.
<f00b4r0> there's a -lpthread missing on that libtool line
<f00b4r0> wild guess, we have HAVE_PTHREAD=1 in zstd build, it probably needs to have -lpthread when -lzstd is set
<f00b4r0> wonder why this didn't break locally
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/96/builds/149) of `master_qualcommax/ipq807x` failed.
<f00b4r0> -pthread*
<f00b4r0> staging_dir/host/lib/pkgconfig/libzstd.pc specifies -pthread in Libs.private
<f00b4r0> I suspect this is related to using a static build
<f00b4r0> Ansuel: ping?
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/182/builds/148) of `master_bmips/bcm6318` failed.
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/153/builds/148) of `master_bmips/bcm6328` failed.
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/141/builds/148) of `master_kirkwood/generic` failed.
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/167/builds/148) of `master_bmips/bcm6362` failed.
<Ansuel> f00b4r0 pong?
<owrt-images-builds> Build [#146](https://buildbot.openwrt.org/images/#/builders/151/builds/146) of `master_layerscape/armv7` failed.
<f00b4r0> see above
<Ansuel> did you manage to find the cause?
<f00b4r0> i think we have a dependency issue
<f00b4r0> I don't fully understand why we're doing a static build but I suspect that's part of the problem
<owrt-images-builds> Build [#58](https://buildbot.openwrt.org/images/#/builders/238/builds/58) of `master_d1/generic` failed.
<Ansuel> it wasn't a problem with gdb ?
<f00b4r0> no it's a linkage problem, see https://pastebin.com/WJ9hj360
<f00b4r0> it calls -lzstd but without -pthread and so pthread symbols (from libzstd presumably) are unresolved
<f00b4r0> or it's pulling something from the host (since I didn't trigger this problem locally)
<owrt-images-builds> Build [#147](https://buildbot.openwrt.org/images/#/builders/193/builds/147) of `master_mvebu/cortexa9` failed.
<Ansuel> Libs: -L${libdir} -lzstd
<Ansuel> Libs.private: -pthread
<owrt-images-builds> Build [#153](https://buildbot.openwrt.org/images/#/builders/165/builds/153) of `master_at91/sama7` failed.
<f00b4r0> yes that's what I pointed out. But obviously the Libs.private isn't being used here
<f00b4r0> I just checked, the POOL_* symbols are from libzstd.a
<f00b4r0> so it has an implicit dep on pthread which isn't passed to subsequent builds
<f00b4r0> I have zero pkg-config skills so I don't know how to fix that
<Ansuel> Libs.private: The link flags for private libraries required by this package but not exposed to applications. The same rule as Cflags applies here.
<Ansuel> -pthread should be moved to libs with static probably
<Ansuel> let me check zstd
<Ansuel> When linking a POSIX program with a multithreaded version of libzstd, note that it's necessary to invoke the -pthread flag during link stage.
<Ansuel> but i though that was handled in pkg-config
<owrt-images-builds> Build [#147](https://buildbot.openwrt.org/images/#/builders/154/builds/147) of `master_armsr/armv7` failed.
<f00b4r0> it probably is handled for the shared lib
<f00b4r0> but we're doing something extra special here
<f00b4r0> "When building with make, by default the dynamic library is multithreaded and static library is single-threaded (for compatibility reasons)."
<f00b4r0> I'm going to bet these "compatibility reasons" are what we're seeing now :)
<owrt-images-builds> Build [#151](https://buildbot.openwrt.org/images/#/builders/190/builds/151) of `master_at91/sam9x` failed.
<f00b4r0> note: "Force enable multithreading on both dynamic and static libraries by appending -mt to the target, e.g. make lib-mt"
<f00b4r0> maybe that's what we should be using?
<f00b4r0> i.e. +$(MAKE) $(HOST_JOBS) -C $(HOST_BUILD_DIR)/lib-mt install-pc install-static PREFIX=$(HOST_BUILD_PREFIX)
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/125/builds/149) of `master_bcm47xx/mips74k` failed.
<owrt-images-builds> Build [#154](https://buildbot.openwrt.org/images/#/builders/62/builds/154) of `master_at91/sama5` failed.
<owrt-images-builds> Build [#152](https://buildbot.openwrt.org/images/#/builders/29/builds/152) of `master_apm821xx/sata` failed.
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/127/builds/149) of `master_malta/be` failed.
<owrt-images-builds> Build [#147](https://buildbot.openwrt.org/images/#/builders/211/builds/147) of `master_mediatek/mt7623` failed.
<owrt-images-builds> Build [#152](https://buildbot.openwrt.org/images/#/builders/26/builds/152) of `master_mediatek/mt7629` failed.
<stintel> ping dangole
<f00b4r0> Ansuel: I suspect that the reason why it didn't fail locally is because I have libzstd1 installed and it probably picked that up instead of the staging_dir one. This suggests we still pull in host bits, alas
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/80/builds/150) of `master_armsr/armv8` failed.
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/101/builds/150) of `master_bmips/bcm6368` failed.
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/124/builds/148) of `master_bcm27xx/bcm2710` failed.
<Ansuel> thing is gdb worked previusly right?
<Ansuel> and zstd was still used as a dependency
<f00b4r0> it wasn't built the same way
<f00b4r0> specifically, I don't think it was statically built (or it's not obvious from the build recipe)
<Ansuel> yes it was
<f00b4r0> then maybe the pc was different?
<Ansuel> check the meson build args
<stintel> looking at this patch: mtd: ubi: provide NVMEM layer over UBI volumes
<Ansuel> i have an old buildroot so i'm checking just that
<stintel> the EAP683-LR has mt76 caldata in a file on UBI filesystem
<Ansuel> Name: libzstd
<Ansuel> Description: fast lossless compression algorithm library
<Ansuel> Version: 1.5.5
<Ansuel> Libs: -L${libdir} -lzstd -pthread
<f00b4r0> well I don't know if '-Ddefault_library=static' has the same consequences as 'make install-static'
<Ansuel> Cflags: -I${includedir} -pthread
<stintel> I'm just not seeing how to refer to a filename with nvmem-layout
<f00b4r0> there you go
<stintel> wait
<Ansuel> well yep meson pkg-config just adds -pthread
<stintel> maybe I do
<f00b4r0> Ansuel: maybe make lib-mt is the fix?
<f00b4r0> given the README suggestion
* f00b4r0 tries
<owrt-images-builds> Build [#153](https://buildbot.openwrt.org/images/#/builders/13/builds/153) of `master_lantiq/xrx200` failed.
<Ansuel> IMHO it's more of a problem in the makefile and meson fixing it under the hood
<owrt-images-builds> Build [#153](https://buildbot.openwrt.org/images/#/builders/82/builds/153) of `master_realtek/rtl930x` failed.
<f00b4r0> oh we already do lib-mt
<f00b4r0> silly me
<f00b4r0> Ansuel: well at least we know *where* the problem is :)
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/226/builds/150) of `master_ath79/tiny` failed.
<Ansuel> i have the downstream patch ready to fix the pc.in file
<owrt-images-builds> Build [#145](https://buildbot.openwrt.org/images/#/builders/136/builds/145) of `master_x86/geode` failed.
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/109/builds/148) of `master_bmips/bcm63268` failed.
<Ansuel> but i'm searching if my theory about meson doing STUFF is correct
<Ansuel> ok yep meson pkgconfig logic is totally different...
<Ansuel> maybe I can create a not shit enough patch to have this merged in zstd
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/194/builds/149) of `master_ramips/rt288x` failed.
<f00b4r0> Ansuel: goes to show that using 3rd-party build recipes may be another vector ;P
<f00b4r0> but I agree this should probably be fixed upstream Makefile
<f00b4r0> +in
<owrt-images-builds> Build [#152](https://buildbot.openwrt.org/images/#/builders/164/builds/152) of `master_ath79/nand` failed.
<f00b4r0> Ansuel: that aside we really need to harden our build recipe to stop using standard library search path. Dunno if it can easily be done though
<Ansuel> it's possible... my dream some month ago was to swich our ci to use an alpine image
<Ansuel> but the fact that alpine use musl instead of glibc cause some trouble with our host tools
<Ansuel> there is alpine-debian but mhe...
<f00b4r0> robimarko pointed out earlier that even minimal-alpine has zstd
<Ansuel> some user also use nix since there were some commit that fixed some bugs with it
<f00b4r0> I think unless we can be absolutely sure we forbid the default search path for ld, we will never be safe, regardless of the underlying os
<owrt-images-builds> Build [#168](https://buildbot.openwrt.org/images/#/builders/4/builds/168) of `master_mvebu/cortexa53` failed.
<f00b4r0> just a handful more builds to fail and then we should have quiet again ;)
<Ansuel> did you manage to repro the bug ?
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/155/builds/150) of `master_sunxi/cortexa8` failed.
<owrt-images-builds> Build [#152](https://buildbot.openwrt.org/images/#/builders/52/builds/152) of `master_ramips/mt76x8` failed.
<owrt-images-builds> Build [#152](https://buildbot.openwrt.org/images/#/builders/188/builds/152) of `master_realtek/rtl931x` failed.
<f00b4r0> Ansuel: I can't, due to having libzstd locally
<f00b4r0> and I can't uninstall that because world+dog depends on it
<KGB-2> https://tests.reproducible-builds.org/openwrt/openwrt_bcm47xx.html has been updated. (100.0% images and 100.0% packages reproducible in our current test framework.)
<f00b4r0> i would have caught the issue earlier otherwise, but my testbuild of master+#14619 went through mighty fine
<f00b4r0> testbuild == buildbot .config
<f00b4r0> ugh, Nick Hainke pushed a revert. The failure dance is restarted
<f00b4r0> lets' pause the buildbots maybe?
<f00b4r0> Ansuel: I'd suggest pushing a quick temporary patch to pc.in to add -pthread and then revisit with an upstream fix later, maybe?
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/93/builds/150) of `master_ramips/mt7620` failed.
<Ansuel> yep just pushed the commit (i verified the generated .pc match the one from meson)
<f00b4r0> oh you did even better
<f00b4r0> nice
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/168/builds/150) of `master_imx/cortexa7` failed.
<Ansuel> and i'm creating a branch and proposing this upstream
<owrt-images-builds> Build [#152](https://buildbot.openwrt.org/images/#/builders/43/builds/152) of `master_imx/cortexa9` failed.
<f00b4r0> very cool
<owrt-images-builds> Build [#145](https://buildbot.openwrt.org/images/#/builders/104/builds/145) of `master_layerscape/armv8_64b` failed.
<owrt-images-builds> Build [#151](https://buildbot.openwrt.org/images/#/builders/217/builds/151) of `master_bcm47xx/generic` failed.
<owrt-images-builds> Build [#151](https://buildbot.openwrt.org/images/#/builders/198/builds/151) of `master_ath79/mikrotik` failed.
<f00b4r0> we'll have another 3 failures then the builders will catch the current HEAD
<Ansuel> only 5 minutes to make it fail
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/163/builds/148) of `master_gemini/generic` failed.
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/231/builds/150) of `master_mpc85xx/p1010` failed.
<Ansuel> but still it does fail on gdb wonder why...
<f00b4r0> these are still old failures
<f00b4r0> ignore them
<f00b4r0> there will be one more
<f00b4r0> or maybe not ;)
<Ansuel> >:(
<Ansuel> mhhh no new build got triggered?
<f00b4r0> it should happen any moment now
<f00b4r0> tree must be stable for 15mn before builds are triggered, and we just crossed that
<Ansuel> there we go
<Ansuel> btw the ccache thing is run locally and wiped every time?
<f00b4r0> i'm not sure I understand?
<Ansuel> 2 s property 'ccache_command' set6 ccache
<Ansuel> we use ccache on buildbot?
<f00b4r0> only for tool
<f00b4r0> s
<f00b4r0> tools and tar, actually
<Ansuel> oh ok now i have to understand why the hell nginx is broken on mips -.-
<f00b4r0> heh, can't help you with that I'm afraid
<Ansuel> got triggered when LTO was enabled
<Ansuel> but only for mips...
<f00b4r0> oh zstd have a soul-sucking CLA
<f00b4r0> well it seems to be telling you exactly what it wants? :)
<f00b4r0> toolchain built successfully on buildbost
<Ansuel> well it seems the patch did the trick
<Ansuel> yep
enyc has quit [Ping timeout: 480 seconds]
<f00b4r0> Ansuel: re your build failure, I suspect it may be related to different flags passed to gcc between object build and final link
<f00b4r0> specifically, -fPIC is missing from the latter
<stintel> aha, got wifi working on the EAP683-LR
<f00b4r0> iirc when using LTO, great care must be taken for consistent build flags or shit may happen
<Ansuel> mhhh where did you notice -fpic is missing?
<f00b4r0> look at the few lines above the beginning of the error messages
<f00b4r0> and the ones above that that do the link step (gcc -o FOO.so FOO.o BAR.o BAZ.o etc)
<f00b4r0> none of these specify -fPIC, but all the objects are built with -fPIC (further up in the log)
<f00b4r0> i think that's why it fails and why it complains that you need to recompile with -fPIC
<f00b4r0> put differently: the objects were built for position independent code, but the final shared object isn't. That's why it fails (i think)
<f00b4r0> anyhow, I'm off; bbiaw
<Ansuel> oh wow core is not build -fpic but addons are
<stintel> time to run dl_cleanup it seems
<stintel> holy shit already running for 3 minutes
<stintel> this was long overdue
rua has joined #openwrt-devel
<Ansuel> ok good i at least manage to repro the error
skynet2 has joined #openwrt-devel
dangole has joined #openwrt-devel
<owrt-images-builds> Build [#169](https://buildbot.openwrt.org/images/#/builders/4/builds/169) of `master_mvebu/cortexa53` completed successfully.
<f00b4r0> Ansuel: also beware that -fpic != -fPIC
<f00b4r0> stintel: i didn't even know about dl_cleanup ;P
<stintel> now you do ;)
<f00b4r0> rm -rf works just fine :D
<stintel> right I was going to grab my laptop and connect to the EAP683-LR via Wi-Fi so I can take a nanddump
<f00b4r0> :)
<stintel> or maybe just do client mode
<stintel> nanddump: error!: mtd_get_dev_info failed
<stintel> hmmz
<svanheule> mirko: the GS1900-24E(P) is a different form factor than the GS1900-24(P), so that port order may be a restriction of the PCB layout. And I agree that poe_enable node isn't pretty
rz has joined #openwrt-devel
<svanheule> mirko: uart1 being defined-but-disabled is because, as part of the SoC, it is always present (but not always used)
<svanheule> mirko: where/how would rather see the realtek-poe package being provided? there was some discussion about splitting the package here: https://github.com/Hurricos/realtek-poe/pull/31
<Ansuel> f00b4r0 well -fPIC was present in cflags but missing in ldflags
<Ansuel> aka it was missing on linking
<f00b4r0> this explains that
skynet2 has quit [Ping timeout: 480 seconds]
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/205/builds/149) of `master_mpc85xx/p1020` completed successfully.
skynet2 has joined #openwrt-devel
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/61/builds/148) of `master_ramips/mt7621` completed successfully.
<owrt-images-builds> Build [#154](https://buildbot.openwrt.org/images/#/builders/85/builds/154) of `master_bcm53xx/generic` completed successfully.
<owrt-images-builds> Build [#153](https://buildbot.openwrt.org/images/#/builders/97/builds/153) of `master_ixp4xx/generic` completed successfully.
dannyAAM has quit [Quit: znc.saru.moe : ZNC 1.6.2 - http://znc.in]
<owrt-images-builds> Build [#154](https://buildbot.openwrt.org/images/#/builders/99/builds/154) of `master_bcm4908/generic` completed successfully.
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
<owrt-images-builds> Build [#151](https://buildbot.openwrt.org/images/#/builders/138/builds/151) of `master_bcm27xx/bcm2708` completed successfully.
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/110/builds/148) of `master_zynq/generic` completed successfully.
<Ansuel> ahhh so much green *.*
<owrt-images-builds> Build [#173](https://buildbot.openwrt.org/images/#/builders/1/builds/173) of `master_ipq40xx/chromium` completed successfully.
<f00b4r0> ;)
<dangole> <3
<owrt-images-builds> Build [#153](https://buildbot.openwrt.org/images/#/builders/19/builds/153) of `master_apm821xx/nand` completed successfully.
<stintel> dangole: for that caldata on ubifs, would it be acceptable to configure the ubi volume containing the ubifs in the DTS, so that it's attached during boot, or would you handle attach and mount also in userspace ?
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/45/builds/150) of `master_sunxi/cortexa7` completed successfully.
<stintel> dangole: also, do you have any suggestions to try to make ethernet work? link is detected but I'm not seeing any traffic, tried both mac@0 and mac@1, no GPL dump available, I've requested it from TP-Link today
<owrt-images-builds> Build [#157](https://buildbot.openwrt.org/images/#/builders/9/builds/157) of `master_pistachio/generic` completed successfully.
<f00b4r0> so it turns out gnu git repos are accessible over http
<owrt-images-builds> Build [#168](https://buildbot.openwrt.org/images/#/builders/8/builds/168) of `master_oxnas/ox820` completed successfully.
* f00b4r0 is going through the remaining .tar.xz tools
<stintel> ah, putting the ubi factory volume in the dts causes that to be ubi0, and then boot fails because there is no /dev/ubiblock0_0
<owrt-images-builds> Build [#146](https://buildbot.openwrt.org/images/#/builders/210/builds/146) of `master_rockchip/armv8` completed successfully.
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/204/builds/148) of `master_sunxi/cortexa53` completed successfully.
minimal has joined #openwrt-devel
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/185/builds/148) of `master_ipq806x/generic` completed successfully.
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/234/builds/149) of `master_ipq40xx/mikrotik` completed successfully.
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/220/builds/150) of `master_mpc85xx/p2020` completed successfully.
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/142/builds/149) of `master_bcm27xx/bcm2711` completed successfully.
robimarko has joined #openwrt-devel
<owrt-images-builds> Build [#146](https://buildbot.openwrt.org/images/#/builders/115/builds/146) of `master_x86/64` completed successfully.
<owrt-images-builds> Build [#156](https://buildbot.openwrt.org/images/#/builders/25/builds/156) of `master_realtek/rtl838x` completed successfully.
<f00b4r0> robimarko: so I took a look at the remaining tools Makefiles that pull .tar.xz
<f00b4r0> turns out the gnu utils are available over http(s) git
<f00b4r0> and the others are on GH
<f00b4r0> dunno if it's worth the effort
<robimarko> Not really sure
<robimarko> BTW, I am looking at IRC log
<robimarko> What was the root cause of GDB python?
<f00b4r0> it wasn't the cause of failure
<owrt-images-builds> Build [#151](https://buildbot.openwrt.org/images/#/builders/63/builds/151) of `master_lantiq/xway` completed successfully.
<f00b4r0> the cause of failure was missing -pthread LDFLAG
<f00b4r0> which I traced down to using the statically linked variant of zstd, but which shipped a .pc that didn't pass the flag
<owrt-images-builds> Build [#143](https://buildbot.openwrt.org/images/#/builders/219/builds/143) of `master_ath79/generic` completed successfully.
<robimarko> Oh, I am reading the commit now
<f00b4r0> Ansuel kindly cooked a patch
<robimarko> Its rather crazy
<f00b4r0> it took a bit of rabbit-holeing yeah :)
<robimarko> Speaking of rabbit-holes
<f00b4r0> robimarko: btw if you want to convert llvm-bpf package, I think it's the only one missing
<robimarko> Somehow this random package hash is broken still
<f00b4r0> sms-tools?
<f00b4r0> lets see if I can repro
<f00b4r0> could this be an apk-related thing?
<f00b4r0> it uses PKG_SOURCE_DATE
<robimarko> It shouldnt, not for the hash
<f00b4r0> actually, unfold the errors
<f00b4r0> it tries to dl .tar.xz, fails that, falls back to git, then the check compares with .tar.xz
<f00b4r0> so of course that's going to fail
<robimarko> Yeah
<robimarko> Its probably outdated tooling
<robimarko> Cause buildbots just kicked in high gear
<robimarko> Cause I think they are using SDK for the tests
<owrt-images-builds> Build [#147](https://buildbot.openwrt.org/images/#/builders/38/builds/147) of `master_x86/generic` completed successfully.
<f00b4r0> i can't reproduce locally. make check passes
<f00b4r0> oh wait stupid me
<f00b4r0> Im' not testing the PR
<f00b4r0> same player tries again
<f00b4r0> still works
<robimarko> OK, lets give buildbots some time to generate all of the SDK-s
<robimarko> As its clearly using one without all of the changes
<owrt-images-builds> Build [#106](https://buildbot.openwrt.org/images/#/builders/237/builds/106) of `master_bcm27xx/bcm2712` completed successfully.
dannyAAM has joined #openwrt-devel
<owrt-images-builds> Build [#146](https://buildbot.openwrt.org/images/#/builders/189/builds/146) of `master_mediatek/mt7622` completed successfully.
<owrt-images-builds> Build [#154](https://buildbot.openwrt.org/images/#/builders/173/builds/154) of `master_lantiq/ase` completed successfully.
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/187/builds/150) of `master_lantiq/xway_legacy` completed successfully.
<owrt-images-builds> Build [#15](https://buildbot.openwrt.org/images/#/builders/240/builds/15) of `master_imx/cortexa53` completed successfully.
<owrt-images-builds> Build [#151](https://buildbot.openwrt.org/images/#/builders/94/builds/151) of `master_ipq806x/chromium` completed successfully.
<hauke> nbd: I am looking into TLS 1.3 support with mbedtls, I saw that you are also looking into it
dannyAAM has quit [Remote host closed the connection]
<mrnuke> svanheule: If we can somehow get kernel 6.1 on realtek, I'd be interested to look into adding PSE functionality to the tps23861 driver
dannyAAM has joined #openwrt-devel
<mrnuke> svanheule: I realize it's just a handful of TP-Link switcces that would benefit
<owrt-images-builds> Build [#151](https://buildbot.openwrt.org/images/#/builders/162/builds/151) of `master_bmips/bcm6358` completed successfully.
<robimarko> mrnuke: That is just the bare minimum
<mrnuke> robimarko: great! I have a ready-written example :D
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/206/builds/150) of `master_bcm47xx/legacy` completed successfully.
<owrt-images-builds> Build [#151](https://buildbot.openwrt.org/images/#/builders/68/builds/151) of `master_octeontx/generic` completed successfully.
<owrt-images-builds> Build [#147](https://buildbot.openwrt.org/images/#/builders/157/builds/147) of `master_mvebu/cortexa72` completed successfully.
<owrt-images-builds> Build [#44](https://buildbot.openwrt.org/images/#/builders/239/builds/44) of `master_starfive/generic` completed successfully.
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/193/builds/148) of `master_mvebu/cortexa9` completed successfully.
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/96/builds/150) of `master_qualcommax/ipq807x` completed successfully.
<owrt-images-builds> Build [#59](https://buildbot.openwrt.org/images/#/builders/238/builds/59) of `master_d1/generic` completed successfully.
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/153/builds/149) of `master_bmips/bcm6328` completed successfully.
<svanheule> mrnuke: have you seen https://forum.openwrt.org/t/187441 ? It's VLANs holding things up. I haven't been able to put much time into the issue yet :-/
<svanheule> mrnuke: robimarko: I'm also looking forward to being able to use the kernel PoE framework :-)
<owrt-images-builds> Build [#154](https://buildbot.openwrt.org/images/#/builders/165/builds/154) of `master_at91/sama7` completed successfully.
<svanheule> PD692x0 support would be really nice for my Cisco SG220
<robimarko> PD692x0 is quite popular in switches so we chose it for the reference
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/141/builds/149) of `master_kirkwood/generic` completed successfully.
<mrnuke> svanheule: I haven't been able to follow the thread. Believe it or not, all four of my realtek switches with PoE are in use
<owrt-images-builds> Build [#153](https://buildbot.openwrt.org/images/#/builders/29/builds/153) of `master_apm821xx/sata` completed successfully.
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/167/builds/149) of `master_bmips/bcm6362` completed successfully.
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/154/builds/148) of `master_armsr/armv7` completed successfully.
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/125/builds/150) of `master_bcm47xx/mips74k` completed successfully.
<owrt-images-builds> Build [#152](https://buildbot.openwrt.org/images/#/builders/190/builds/152) of `master_at91/sam9x` completed successfully.
dannyAAM has quit [Remote host closed the connection]
dannyAAM has joined #openwrt-devel
<owrt-images-builds> Build [#147](https://buildbot.openwrt.org/images/#/builders/151/builds/147) of `master_layerscape/armv7` completed successfully.
<mrnuke> Any idea why "mhi mhi0: Image transfer failed" would fail on an IPQ chip? All the references I could fins balme it on "bad firmware"
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/148/builds/149) of `master_bcm27xx/bcm2709` completed successfully.
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/127/builds/150) of `master_malta/be` completed successfully.
<owrt-images-builds> Build [#148](https://buildbot.openwrt.org/images/#/builders/211/builds/148) of `master_mediatek/mt7623` completed successfully.
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/124/builds/149) of `master_bcm27xx/bcm2710` completed successfully.
<Mangix> Ansuel: meson is a lot simpler than Make and CMake. pkgconfig files don't have to be a manual mess.
<Mangix> Besides that, meson benefits from having way better defaults than CMake.
<Habbie> <3 meson
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/182/builds/149) of `master_bmips/bcm6318` completed successfully.
<Mangix> I tried proposing meson versions of core openwrt libraries. Rejected.
<Habbie> oh why?
* Mangix looks
<mirko> svanheule: point re port order and splitting dts off into a common part is, that the port order on the 24ep is correct while for the 24e even and uneven port numbers are flipped (according to current DTS at least)
<mirko> hence the common part of the two is rather minimal
<mirko> so i consider the PR valid as it is
<Mangix> hmmm can't find it. From what I remember, core developers were happy with CMake
<Habbie> ah
<owrt-images-builds> Build [#153](https://buildbot.openwrt.org/images/#/builders/26/builds/153) of `master_mediatek/mt7629` completed successfully.
<f00b4r0> countless reports of packages updating meson resulting in FTBFS unless you run bleeding edge meson
<f00b4r0> meson breaking on python update or vice-versa
<owrt-images-builds> Build [#151](https://buildbot.openwrt.org/images/#/builders/80/builds/151) of `master_armsr/armv8` completed successfully.
<f00b4r0> we don't need such a stable build system I think.
<Mangix> meson breaking on python update?
<Mangix> that is highly specific
<Mangix> Ubuntu 18.04 is no longer supported.
<f00b4r0> just top of quick search
<Mangix> that's the same bug
<f00b4r0> yeah and it's great not to be able to build older releases after a few years
<f00b4r0> such a feature.
<f00b4r0> I can grab a source archive that uses 'make' from 20y ago and build it just fine.
<robimarko> CMake is also quite good for supporting rather old CMake recipes
<robimarko> For core tools meson changing minimal python is not good
<f00b4r0> meson is as broken as python is, from a stability PoV. Let's not spread this cancer further
<owrt-images-builds> Build [#151](https://buildbot.openwrt.org/images/#/builders/101/builds/151) of `master_bmips/bcm6368` completed successfully.
<Mangix> fake news.
<f00b4r0> robimarko: currently test building your last push to 14619 :)
<Mangix> from working on various packages, meson tends to be the least broken.
<f00b4r0> for about 2 weeks
<f00b4r0> then you can no longer build the archive.
<robimarko> Again, what good is it if it decides that python 3.X is now required
<Mangix> robimarko: older versions of meson can be kept in that case. actually, that was the case until 18.04 compatibility was dropped.
<f00b4r0> meson completely eschew backward compatibility. Therefore it's not suitable as a long term build management.
<f00b4r0> QED. Let's move on.
<Mangix> f00b4r0: source?
<Habbie> is muon any help here?
<robimarko> Mangix: Yeah, and then we had packages that cannot be updated because they require meson X but it requires python X and so on
<f00b4r0> openwrt GH
<f00b4r0> and you just admitted "18.04 is no longer supported" so you know it very well
<Mangix> backwards compatibility with older meson versions?
<f00b4r0> makefiles don't suddenly stop working with newer make versions
<Mangix> well actually...
<f00b4r0> I know that may sound incredibly useless to you
<Mangix> I do remember a GNU make update that screwed some packages
<f00b4r0> "a". Assuming it did happen, I suppose it was quickly fixed?
<robimarko> Mangix: How long did it take for Meson 1.X to be merged?
<Mangix> it was with make 4.3 i believe
<owrt-images-builds> Build [#154](https://buildbot.openwrt.org/images/#/builders/82/builds/154) of `master_realtek/rtl930x` completed successfully.
<Mangix> f00b4r0: moot point. meson behaviors can also be patched quickly.
<f00b4r0> no I mean it was fixed in make. Or amply documented and probably only affected some arcane gnu-specific corner cases
<f00b4r0> anyway, we know you won't hear these arguments so let's agree to disagree
<Mangix> no, the packages using deprecated functionality were patched
<f00b4r0> robimarko: build successful. I'll report on PR
<Mangix> robimarko: may 23,2023 vs jun 26,2022
<robimarko> Mangix: well the issue was that some packages also depended on that newer meson that we could not use if older distros like 18.04 were to be supported
<robimarko> Other of the issue that it usually requires quite new Python I dont have anything against it
<robimarko> If anything I find it rather efficient
<Mangix> upstream maintains support for the older supported Ubuntu LTS
<Mangix> once 18.04 became EOL, meson dropped support for python 3.6
<f00b4r0> also how often is make updated? Every 2-4 years typically. Much more conservative.
<robimarko> And the issue is that doesnt really align with our release cadence
<Mangix> actually Canonical backpported Python 3.7 and 3.8 so 18.04. I tried getting patches in to keep it supported in OpenWrt. Rejected.
<Mangix> /s/so/to
<Mangix> it was decided to kill 18.04 support. Not my decision.
robimarko has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
<Mangix> anyway, meson is simpler. You can't do this with make/cmake: https://github.com/openwrt/openwrt/commit/d08ff66fcd786848dcb911a7cb529066a9130343
<Mangix> there was also the pkgconfig issue with zstd that Ansuel had to patch in and add a bunch of code while meson just worked.
<f00b4r0> it's certainly simpler to hide things
<owrt-images-builds> Build [#153](https://buildbot.openwrt.org/images/#/builders/164/builds/153) of `master_ath79/nand` completed successfully.
<Mangix> hmm? pkgconfig is a manual ordeal with both make and cmake
<Mangix> meson has a generator based on the libraries.
<owrt-images-builds> Build [#155](https://buildbot.openwrt.org/images/#/builders/62/builds/155) of `master_at91/sama5` completed successfully.
<owrt-images-builds> Build [#154](https://buildbot.openwrt.org/images/#/builders/13/builds/154) of `master_lantiq/xrx200` completed successfully.
<owrt-images-builds> Build [#151](https://buildbot.openwrt.org/images/#/builders/226/builds/151) of `master_ath79/tiny` completed successfully.
dannyAAM has quit [Quit: znc.saru.moe : ZNC 1.6.2 - http://znc.in]
dannyAAM has joined #openwrt-devel
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/145/builds/150) of `master_octeon/generic` completed successfully.
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/178/builds/150) of `master_sifiveu/generic` completed successfully.
<owrt-images-builds> Build [#150](https://buildbot.openwrt.org/images/#/builders/194/builds/150) of `master_ramips/rt288x` completed successfully.
<mirko> svanheule: could you also tell me, if [2] is supposed to work? because for me (on -24ep) it isn't, but [1] is ( [1] https://paste.nanl.de/?ecd0b36642ff34d5#ANkAigBj428r2SUSeoR3SoesZ4WbKGbhrBjbw6Jtgdw8 [2] https://paste.nanl.de/?3128dca4d2539eab#Dp6ebMBL5Cn38ELyvcrnWLtD5F3pGDDzc5JkoJAyUq6 )
<owrt-images-builds> Build [#153](https://buildbot.openwrt.org/images/#/builders/188/builds/153) of `master_realtek/rtl931x` completed successfully.
<owrt-images-builds> Build [#158](https://buildbot.openwrt.org/images/#/builders/15/builds/158) of `master_mxs/generic` completed successfully.
slh has quit [Quit: leaving]
dannyAAM has quit [Remote host closed the connection]
dannyAAM has joined #openwrt-devel
slh64 has quit [Quit: gone]
<owrt-images-builds> Build [#146](https://buildbot.openwrt.org/images/#/builders/136/builds/146) of `master_x86/geode` completed successfully.
<owrt-images-builds> Build [#153](https://buildbot.openwrt.org/images/#/builders/52/builds/153) of `master_ramips/mt76x8` completed successfully.
<owrt-images-builds> Build [#155](https://buildbot.openwrt.org/images/#/builders/60/builds/155) of `master_realtek/rtl839x` completed successfully.
<owrt-images-builds> Build [#154](https://buildbot.openwrt.org/images/#/builders/58/builds/154) of `master_ipq40xx/generic` completed successfully.
rz has quit [Remote host closed the connection]
rz has joined #openwrt-devel
<owrt-images-builds> Build [#151](https://buildbot.openwrt.org/images/#/builders/155/builds/151) of `master_sunxi/cortexa8` completed successfully.
<owrt-images-builds> Build [#149](https://buildbot.openwrt.org/images/#/builders/109/builds/149) of `master_bmips/bcm63268` completed successfully.
<owrt-images-builds> Build [#151](https://buildbot.openwrt.org/images/#/builders/168/builds/151) of `master_imx/cortexa7` completed successfully.
<owrt-images-builds> Build [#152](https://buildbot.openwrt.org/images/#/builders/217/builds/152) of `master_bcm47xx/generic` completed successfully.
gch981213 has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
slh has joined #openwrt-devel
<owrt-images-builds> Build [#151](https://buildbot.openwrt.org/images/#/builders/126/builds/151) of `master_tegra/generic` completed successfully.
parazyd has quit [Ping timeout: 480 seconds]
<owrt-images-builds> Build [#151](https://buildbot.openwrt.org/images/#/builders/93/builds/151) of `master_ramips/mt7620` completed successfully.
<owrt-images-builds> Build [#146](https://buildbot.openwrt.org/images/#/builders/137/builds/146) of `master_x86/legacy` completed successfully.
<owrt-images-builds> Build [#152](https://buildbot.openwrt.org/images/#/builders/198/builds/152) of `master_ath79/mikrotik` completed successfully.
<owrt-images-builds> Build [#153](https://buildbot.openwrt.org/images/#/builders/43/builds/153) of `master_imx/cortexa9` completed successfully.
<mirko> svanheule: and is that comment of yours (https://github.com/openwrt/openwrt/pull/15081#issuecomment-2041127564) a hint that i should be more descriptive about things?