mainAutoconf - Support: sr #110431, AC_INIT should accept shell...


sr #110431: AC_INIT should accept shell variable expansion in its arguments

Submitter:  Zack Weinberg <zackw>
Submitted:  Sat 23 Jan 2021 08:02:32 PM UTC
Priority:  * 3 - Release N+1 Severity:  1 - Wish
Status:  Confirmed Privacy:  Public
Assigned to:  None Open/Closed:  Open
Operating System:  None
* Mandatory Fields

Add a New Comment Rich Markup

Fri 08 Dec 2023 04:11:18 PM UTC, comment #1: 

I'd like to make this happen for 2.73, but it's not going to happen for 2.72.

Zack Weinberg <zackw>
Group administrator
Sat 23 Jan 2021 08:02:32 PM UTC, original submission:  

Currently, none of the arguments to AC_INIT can be computed when you run 'configure'.  If you use two-argument AM_INIT_AUTOMAKE, on the other hand, you can pass shell variables as the arguments.  The Automake manual calls this out as a reason to continue using two-argument AM_INIT_AUTOMAKE:

> differently from what happens for AC_INIT invocations, this AM_INIT_AUTOMAKE invocation supports shell variables’ expansions in the PACKAGE and VERSION arguments (which otherwise defaults, respectively, to the PACKAGE_TARNAME and PACKAGE_VERSION defined via the AC_INIT invocation; see The AC_INIT macro in The Autoconf Manual); and this can still be useful in some selected situations. Our hope is that future Autoconf versions will improve their support for package versions defined dynamically at configure runtime; when (and if) this happens, support for the two-args AM_INIT_AUTOMAKE invocation will likely be removed from Automake.

So we should find a way to support shell variable expansion in the arguments to AC_INIT.

Zack Weinberg <zackw>
Group administrator


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by zackw (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.


    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-12-08 zackw Priority5 - Unprioritized 3 - Release N+1
        Severity3 - Normal 1 - Wish
        StatusNone Confirmed

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code