| Summary: | Configure creates local .config | ||
|---|---|---|---|
| Product: | Geant4 | Reporter: | clark.mcgrew |
| Component: | config | Assignee: | Ben Morgan <Ben.Morgan> |
| Status: | CLOSED WONTFIX | ||
| Severity: | minor | CC: | clark.mcgrew, Gabriele.Cosmo |
| Priority: | P2 | ||
| Version: | other | ||
| Hardware: | All | ||
| OS: | Linux | ||
*** Bug 462 has been marked as a duplicate of this bug. *** *** 'Serguei.Sadilov@cern.ch' will be responsible for bug 462. *** It will be fixed in coming release of Geant4. 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. |
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.