[Bug default/30051] poke-3.0 lacks some .m4 files, causes autoreconf to fail

[arsen at aarsen dot me]

https://sourceware.org/bugzilla/show_bug.cgi?id=30051

Arsen Arsenović <arsen at aarsen dot me> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |arsen at aarsen dot me

--- Comment #7 from Arsen Arsenović <arsen at aarsen dot me> ---
(In reply to Sergei Trofimovich from comment #6)
> (In reply to Bruno Haible from comment #5)
> > Who says that running autoreconf on an arbitrary GNU package's tarball is
> > supported? In general, it is not supported.
> 
> If it's unsupported on poke release tarballs then please feel free to close
> it as INVALID.
> 
> Having an equivalent procedure would be nice though. Downstreams have to
> patch m4 bits from time to time.
> 
> And optionally add an explicit error message if it's easy in configure.ac so
> people would not repeat the mistake again and again when next platform
> appears and they try `autoreconf -if` again.
> 
> > > nixpkgs repository used autoreconf on previous release of poke to get 
> > > support for new aarch64-darwin and other platforms to get recognized by 
> > > configure.
> > 
> > The tarball now contains the newest config.guess and config.sub. You can
> > ditch that autoreconf invocation.
> 
> Sounds good. That is my current attempt.

If you can affect nixpkgs, I suggest adopting a practice of not regenerating
build system files in autotools projects, and, if some are patched (which is
often necessary, and completely understandable) only re-run the appropriate
tools (the autoconf manual has a nifty, though incomplete, diagram about what
produces what:
https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.71/autoconf#Making-configure-Scripts).
Of course, if building from Git snapshots, you ought to run ``./bootstrap''.

You can safely bump config.{status,guess}, as both are just invocable programs
that configure scripts run, and do not get inlined in any other files.

-- 
You are receiving this mail because:
You are on the CC list for the bug.