This is an enhancement bug for the present build system of g4py. 1. It uses home-made configure, isolated from cmake, the official geant build system. This make g4py not well tested during geant release, and get broken frequently. 2. It does not support parallel make. (make -j40 results in 1 thread compiling) 3. It does not exit when a compilation error happens (cf. a) Not sure how these could be fixed though. Comments, Murakami-san? a. http://bugzilla-geant4.kek.jp/show_bug.cgi?id=1544
Sorry, I've found the cmake system of g4py, close as invalid