Project

General

Profile

Bug #1560

Geant 4 building incorrectly

Added by Heidt, Christopher about 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03 October 2014
Due date:
% Done:

100%

Estimated time:
Workflow:
New Issue

Description

Just did a fresh install of the tracker development branch and it looks like geant4 isn't installing correctly. I noticed that the third party bash script is looking for geant4.9.6_build.tar.gz (or something similar to that) when what downloads is a geant4.9.6.p02.tar.gz. I've changed this and ran the build_all.bash script (with all the other installs commented out, and after sourcing env.sh). This did not work, see below for the error it created:

INFO: Found source archive in 'source' directory
INFO: Source archive exists.

INFO: Checking MD5 checksum (otherwise the file didn't
INFO: download properly):

geant4.9.6.p02.tar.gz.md5
geant4.9.6.p02.tar.gz: OK

INFO: Unpacking geant4 source:

INFO: Unpacking geant4 data:

INFO: Generating make files:

-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
-- Check for working C compiler: /home/hep/cheidt/bin/gcc
-- Check for working C compiler: /home/hep/cheidt/bin/gcc -- broken
CMake Error at /home/hep/cheidt/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:52 (MESSAGE):
  The C compiler "/home/hep/cheidt/bin/gcc" is not able to compile a simple
  test program.

  It fails with the following output:

   Change Dir: /home/hep/cheidt/work/one/third_party/build/geant4.9.6.p02/CMakeFiles/CMakeTmp

  Run Build Command:/usr/bin/gmake "cmTryCompileExec2298348798/fast" 

  /usr/bin/gmake -f CMakeFiles/cmTryCompileExec2298348798.dir/build.make
  CMakeFiles/cmTryCompileExec2298348798.dir/build

  gmake[1]: Entering directory
  `/home/hep/cheidt/work/one/third_party/build/geant4.9.6.p02/CMakeFiles/CMakeTmp'

  /home/hep/cheidt/bin/cmake -E cmake_progress_report
  /home/hep/cheidt/work/one/third_party/build/geant4.9.6.p02/CMakeFiles/CMakeTmp/CMakeFiles
  1

  Building C object
  CMakeFiles/cmTryCompileExec2298348798.dir/testCCompiler.c.o

  /home/hep/cheidt/bin/gcc -o
  CMakeFiles/cmTryCompileExec2298348798.dir/testCCompiler.c.o -c
  /home/hep/cheidt/work/one/third_party/build/geant4.9.6.p02/CMakeFiles/CMakeTmp/testCCompiler.c

  gmake[1]: execvp: /home/hep/cheidt/bin/gcc: Permission denied

  gmake[1]: *** [CMakeFiles/cmTryCompileExec2298348798.dir/testCCompiler.c.o]
  Error 127

  gmake[1]: Leaving directory
  `/home/hep/cheidt/work/one/third_party/build/geant4.9.6.p02/CMakeFiles/CMakeTmp'

  gmake: *** [cmTryCompileExec2298348798/fast] Error 2

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:36 (project)

-- Configuring incomplete, errors occurred!

INFO: Running make:

make: *** No targets specified and no makefile found.  Stop.

INFO: Installing:

make: *** No rule to make target `install'.  Stop.

INFO: Cleaning up

INFO: The package should be locally build now in your
INFO: third_party directory, which the rest of MAUS will
INFO: find.
INFO: making environment

trying to run scons, I get the following error:

Checking for C++ header file Geant4/G4EventManager.hh... no
#1

Updated by Dobbs, Adam about 8 years ago

Hi Chris. Looking at the output you post, the first error I see is about your compiler, rather than about GEANT itself. Perhaps try looking at that first?

#2

Updated by Heidt, Christopher about 8 years ago

Yeah I saw that too, I started a full rebuild when I posted this, it is currently ongoing. I figured since I knew at least one thing was wrong, I would put this up here.

#3

Updated by Dobbs, Adam about 8 years ago

OK, I just did a clean pull and rebuild myself, no problems seen. Let me know if this persists.

#4

Updated by Heidt, Christopher about 8 years ago

Interesting, I've been poking around with it and still can't get it to build geant. Everything else seems to be building find though. Can you do me a favor and look for what version of geant is installing on your machine. Check the third party sources for the tar.gz file and look in the "build_all.bash".

My path is pointing to my home bin directory and there is definitely a compiler in there.

#5

Updated by Dobbs, Adam about 8 years ago

Sure, it's GEANT4.9.6

#6

Updated by Rajaram, Durga about 8 years ago

It looks like it's the compiler somehow
In the original log you posted:

gmake[1]: execvp: /home/hep/cheidt/bin/gcc: Permission denied

Can you check the permission on /home/hep/cheidt/bin/gcc ?
Also the cmake version?
Are you doing [ or have you tried ] a clean build?

#7

Updated by Dobbs, Adam about 8 years ago

Are you build on either the ral ppd or ic clusters Chris?

#8

Updated by Heidt, Christopher about 8 years ago

Rebuilt this afternoon on an Imperial machine, with my home builds removed from PATH. I think that may have done the trick. GEANT4 looks like it built, still need to test though. Unfortunately, building a the newest version of gcc meant I don't have any quota left at Imperial, so I need to clean that up and rebuild MAUS again.

Adam, do you know of any way of getting over 1.7 GB of storage space on the Imperial machines, seriously cramps my considerable style.

#9

Updated by Dobbs, Adam about 8 years ago

Make yourself a directory under:

/vols/mice3/

It's a joint disk, so be mindful of your usage.

#10

Updated by Heidt, Christopher about 8 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

Not an issue

Also available in: Atom PDF