Project

General

Profile

Bug #1746

build --help needs information from src/scripts/configure

Added by Jim Phillips 7 months ago. Updated 5 months ago.

Status:
Merged
Priority:
Normal
Assignee:
Category:
Build & Test Automation
Target version:
Start date:
11/16/2017
Due date:
% Done:

0%


Description

Running build --help produces the following error:

Advanced options:
:./build: line 81: ./src/scripts/configure: No such file or directory
./build: line 82: ./src/scripts/configure: No such file or directory
  bigemulator     compile for BigSim simulator
  ooc             compile with out of core support
  syncft          compile with Charm++ fault tolerance support
  mlogft          compile with Charm++ message logging fault tolerance support
  papi            compile with PAPI performance counter support (if any)

History

#1 Updated by Jim Phillips 7 months ago

Error was showing up in the wrong place due the the paginator. It's actually in the "Enable/disable features" section, which runs configure --help.

Enable/disable features:
./build: line 81: ./src/scripts/configure: No such file or directory
./build: line 82: ./src/scripts/configure: No such file or directory
  --with-production       build Charm++ with all optimizations for maximum performance, and disabling all above features

#2 Updated by Sam White 7 months ago

  • Target version set to 6.9.0
  • Assignee set to Evan Ramos

#3 Updated by Evan Ramos 7 months ago

This was caused by the removal of configure from the git repository, which is now regenerated from configure.ac during the build process. We run autoreconf before packaging a tarball, so `./build --help` should work fine there. I'm not sure how best to handle the problem when building directly from git.

#4 Updated by Jim Phillips 7 months ago

What is the command to run autoreconf without creating a build directory?

#5 Updated by Phil Miller 7 months ago

package-tarbahll.sh should get you a readily-built tarball snapshot, with the configure script and other bits suitably generated.

#6 Updated by Evan Ramos 5 months ago

  • Status changed from New to Implemented
  • Category changed from Machine Layers to Build & Test Automation

#7 Updated by Sam White 5 months ago

  • Status changed from Implemented to Merged

Also available in: Atom PDF