Problem 461 - Configure creates local .config
Summary: Configure creates local .config
Status: CLOSED WONTFIX
Alias: None
Product: Geant4
Classification: Unclassified
Component: config (show other problems)
Version: other
Hardware: All Linux
: P2 minor
Assignee: Ben Morgan
URL:
: 462 (view as problem list)
Depends on:
Blocks:
 
Reported: 2003-02-24 08:44 CET by clark.mcgrew
Modified: 2009-09-29 13:31 CEST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this problem.
Description clark.mcgrew 2003-02-24 08:44:36 CET 
In GEANT4.5.0 the Configure command creates a local .config every time it is
run.  This is a problem when Configure -?, when it is used to query for compiler
and load options.  For example, "${G4INSTALL}/Configure -h" attempts to create
"./.config".  This prevents the Configure command from being used in directories
where the user might not have write access.
Comment 1 Gabriele Cosmo 2003-02-24 09:29:59 CET 
*** Bug 462 has been marked as a duplicate of this bug. ***
*** 'Serguei.Sadilov@cern.ch' will be responsible for bug 462. ***
Comment 2 Serguei.Sadilov 2003-10-27 10:52:59 CET 
It will be fixed in coming release of Geant4.
Comment 3 Ben Morgan 2009-09-29 13:30:09 CEST 
Just cleaning this one up....

The problem of a local .config is fairly fundamental to MetaConfig's design so it cannot be fixed without severely breaking other functionality.

The requirement to query the Geant4 installation for flags etc will be factored into a separate script(s) created at build/install time.