autogen.sh fails when using v1.0.tar.gz
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 122
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
System information
- Using v1.0.tar.gz downloaded from the release page
- On OLCF Summit (but my guess is any other system will have the same issue)
Describe the problem you're observing
Because the tarball is not a git repo, using git describe --always inside the configure.ac AC_INIT() macro causes the autoreconf step to fail.
Describe how to reproduce the problem
> ./autogen.sh
... UnifyFS autogen ...
Running libtoolize...
Running autoreconf...
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4
fatal: not a git repository (or any parent up to mount point /autofs)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
configure.ac:17: error: AC_INIT should be called with package and version arguments
/usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from...
configure.ac:17: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
aclocal: error: echo failed with exit status: 1
autoreconf: aclocal failed with exit status: 1
Please proceed with configuring, compiling, and installing.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect autogen.sh and configure.ac, starting at the AC_INIT() version lookup that invokes git describe. Reproduce the failure by running ./autogen.sh from the v1.0.tar.gz release archive. Done means autoreconf completes successfully for the archive rather than requiring a Git repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100