|Message: compiling examples - G4TMPDIR and G4BINDIR||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
I am trying to compile the examples on an instance of geant4 installed in a system area to which I don't have write access. So following instructions I copied $G4INSTALL/.../N01 to my $HOME and tried to make it. It fails because it tries to write into $G4INSTALL/tmp and $G4INSTALL/bin. So I tried copying the first-level included-makefile into my directory and modifing its values: G4TMPDIR=/tmp and G4BINDIR=".". That did not solve the problem.
On my home system (for which I have root privileges) I simply gave world-write permissions to those 2 directories, and I could make and run the examples, using an absolute path to execute them from $G4INSTALL/bin.
This is Geant 4.0.1 at FNAL, and Geant 4.4.0 at home; both on Linux.
So how do I compile the examples without root access and without completely re-installing geant4 under $HOME?
Shouldn't the makefiles test whether these variables are set, and not use hard-coded values for them if the user has set them?
The main purpose of examples is to provide code which users can copy and then modify. This of course includes the makefiles. It is an unwelcome surprise when the executable is built in some far-off directory -- users invariably expect it in ".". IMHO a better design for the makefiles would be to use "." for both these dirs unless the variables are set; that meets user expectations better, while permitting the original usage (with only minor changes).
|Inline Depth:||Outline Depth:||Add message:|