Hi Steve,

OK, I have looked through your log. The G4Analysis issue has cropped up before, even when, as here, GEANT4 looks like it has built perfectly well. I note a few other issues however:

• CDB third party libs failed to build - install yacc (yet-another-compiler) from the Ubuntu repositories (I'll add it to the list of dependencies)
• DOxygen failed to build as bison was missing - install bison and libbison-dev (already a listed dependency, best to make sure everything else listed at http://micewww.pp.rl.ac.uk/projects/maus/wiki/Install, Ubuntu section is installed too (some of the lib names may need a little tweaking when searching for them from the repos))
• G4Beamline failed to build - but you probably won't need it, nor does anything else depend on it, so can ignore

• The latest MAUS version is 3.0.0, I suggest installing that rather than 2.9.1
• GCC will build by default as a third party, however Ubuntu 16 has a sufficiently modern compiler built-in, so you can save huge amount of time and disk space by building with:

./install_build_test.bash --use-system-gcc true -j N

where N is the number of cores you wish to build on (note the gap between the -j and the N).

I strongly suggest rebuilding in clean directory.

Let me know how that goes. If it fails again, we will try something else.

AD

Hi Steve,

Hmmmm, interesting. OK -- could you please send me the exact set of commands you used to start the build, right down to making the directory. It's still hanging on the G4Analysis library...

Best, AD

It's the basic build. I download the source tarball

gunzip MAUS-v.3.0.0.tar.gz
tar xvf MAUS-v3.0.0.tar
cd MAUS-v3.0.0
./install_build_test.bash

• then I let it go....and go....until it hits the G4analysis issue. The "set runtime path " message happens with G4analysis, G4digit, G4error_propagation, and in fact all the other libG4*.so libraries.

All the libraries were built and exist in MAUS-v3.0.0/third_party/install/lib

In this directory there is also a Geant4-9.6.2 directory which seems to contain a self-referential directory link.
In MAUS-v3.0.0/third_party/install/lib/Geant4-9.6.2 there is a directory Linux-g++ which seems to be a link to '..'
(e.g. ls -l this Geant4 directory gives 'Linux-g++ -> ..'). Don't know if that's anything.1

Incidentally - I'll be there tomorrow with my laptop so you can look at the build "in person" if you like....

Excellent - yes a look in person would be helpful. Meanwhile, try using this build command, again in a clean directory:

./install_build_test.bash --use-system-gcc true

This will tell it to build with the Ubuntu in-house gcc, not build gcc separately, which may help.

I have seen this G4 issue before (both Jan and myself have encountered it), but never firmly diagnosed the cause...

The build on Tom's laptop is going well incidentally... I'll race you to a working MAUS version at Warwick.