On 25/02/26 09:53PM, Jelle van der Waa wrote: > Hi All, Heyhey,
> 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. Sounds like a good idea, +1 from me! > 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 Cheers, chris
signature.asc
Description: PGP signature
