On Wed, 2025-02-26 at 21:53 +0100, Jelle van der Waa wrote: > 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.
+1 If autoreconf fails, then it's usually due to missing m4 macros, which indicates either a missing makedependency which contains that macro, or a custom directory needs to be specified by the AC_CONFIG_MACRO_DIR variable [1] within configure.ac which can be fixed by a one-line patch. [2] [1] https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/html_node/Input.html#index-AC_005fCONFIG_005fMACRO_005fDIR-1 [2] https://github.com/notroj/neon/pull/153/files
signature.asc
Description: This is a digitally signed message part
