| Summary: | gmake libmap gives errore | ||
|---|---|---|---|
| Product: | Geant4 | Reporter: | Hans-Peter.Wellisch |
| Component: | config | Assignee: | Serguei.Sadilov |
| Status: | CLOSED WORKSFORME | ||
| Severity: | normal | CC: | Gabriele.Cosmo, Gunter.Folger |
| Priority: | P5 | ||
| Version: | 4.0 | ||
| Hardware: | Sun | ||
| OS: | SunOS | ||
|
Description
Hans-Peter.Wellisch
2002-02-12 07:36:52 CET
"grep -q" is used in source/GNUmakefile for the target "libmap".
The option -q is used to run the command in 'silent' mode:
From "man grep" on sungeant (SunOS 5.7):
-q Quiet. Do not write anything to the standard out-
put, regardless of matching lines. Exit with zero
status if an input line is selected.
The command has changed in SunOS 5.8 ? To be verified.
To verify if the libmap has been generated properly, you can try editing the
file libname.map placed in <your-G4-installation-path>/lib/SUN-CC/ and see if
for example the first line looks like the following:
G4readout: G4globman G4digits G4event G4hits G4tracking G4intercoms G4run
G4track G4geometrymng G4partman G4materials G4volumes G4procman G4detector
Hi folks, this was changed to fixed. Which tag shall I use in future, so I do not get the problem again? Many greetings, Hans-Peter. The report infact has not been toggled to "FIXED", it is "ASSIGNED". Did you try the suggestions I made in my previous posting ? Cheers. Hans Peter, is this not the usual problem of Solaris with its many versions of grep. The one in /usr/bin has NO -q option. The better grep is /usr/xpg4/bin/grep, and this has all the usual options. Do we need to protect for a bad (for G4) PATH set by the user by using an explicit PATH to grep on SUN in the Geant4 setup? hmmmm, /usr/bin is in the default path, so I expect that many people will see the same problem. I would tend to try and take care of it. Many greetings, Hans-Peter. We verified that the problem does not occur in the official reference system at CERN "refsol8" used for the certification of SunOS 5.8. |