Am 26.02.25 um 21:53 schrieb Jelle van der Waa:
Hi All,
After all the recent RISC-V news I went ahead and checked out the
existing effort to get Arch Linux supported on RISC-V. Felix maintains
an overlay of PKGBUILDs which require customization to be be able to
build on RISC-V. A lot of these PKGBUILD's patch autotools projects to
run `autoreconf -fiv` in prepare(), this re-generates `configure` to
understand RISC-V.
Since these patches are simple enough and I don't see them harming
Arch Linux, I would argue that we want these patches applied in our
packages. Re-generating configure should not break, and if it does we
should not accept the patch and get a bug filled upstream.
Re-creating configure and thus not using the provided `configure`
could arguably also be a good thing regarding supply chain security.
And this also should help with other architecture ports.
As a follow up we can discuss providing our own
"/usr/share/config.site" and then ./configure --prefix=/usr would
automatically configure localstatedir, libexecdir, etc.
[1] https://github.com/felixonmars/archriscv-packages
[2]
https://github.com/felixonmars/archriscv-packages/blob/master/libafterimage/riscv64.patch
+ 1 from me too.
--
Tobias Powalowski
Arch Linux Developer (tpowa)
https://www.archlinux.org
tp...@archlinux.org
Archboot Developer
https://archboot.com
St. Martin-Apotheke
Herzog-Georg-Str. 25
89415 Lauingen
https://www.st-martin-apo.de
i...@st-martin-apo.de
