llnl / llnl/LaunchMON

aclocal failure

Open
#56 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
13
Forks
10
PR merge metrics
No merged PRs in 30d

Description

I can't get past the bootstrap because aclocal fail with
```
***** aclocal *****
***** PWD: /var/tmp/portage/sys-cluster/launchmon-1.0.2_p20210430/work/LaunchMON-98ab769c53563f47c4319ce3c98ac394b4870bac
***** aclocal -I config

fatal: not a git repository (or any parent up to mount point /var/tmp)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
configure.ac:93: 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:93: the top level
autom4te-2.69: /usr/bin/m4 failed with exit status: 1
aclocal-1.16: error: autom4te failed with exit status: 1
```
https://github.com/LLNL/LaunchMON/blob/98ab769c53563f47c4319ce3c98ac394b4870bac/configure.ac#L51

How are we supposed to bootstrap from tarballs?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with configure.ac at the linked line and reproduce the bootstrap using the reported `aclocal -I config` command from a tarball rather than a Git checkout. Trace why aclocal attempts Git discovery and why AC_INIT receives no package or version arguments. Done means the tarball bootstrap completes without these errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, git
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.