Geant4 installation ubuntu G4NDL

[Fayzan_Ahmed]

Hello,

I have tried multiple times but always fail on this step of Geant4 installation.

I have been trying to install Geant4 using both Windows and Ubuntu, following multiple tutorials. However, after running the make command, I encounter the following error and multiple errors when I was trying to download on Windows by Visual Studio:
TLSv1.3 (OUT), TLS alert, close notify (256): [2 bytes data] — LOG END —
make[2]: * [CMakeFiles/G4NDL.dir/build.make:99: Externals/G4NDL-4.7.1/src/G4NDL-stamp/G4NDL-download] Error 1
make[1]: * [CMakeFiles/Makefile2:932: CMakeFiles/G4NDL.dir/all] Error 2
make: * [Makefile:156: all] Error 2

I have already downloaded all 15 required Geant4 libraries and datasets from the official website, and they are saved on my hard drive. Could you help me with:

1. How to direct Geant4 to these libraries and datasets during installation to avoid the error if this could help in the installation.
2. Any suggestions to resolve the issue that arises after running make.

Thanks in advance!

[bmorgan]

Sorry for the delay in replying! O.k, if you have the datasets downloaded already separately then:

1. Choose/create a suitable directory to hold the unpacked datasets. This doesn’t have to be anywhere specific, just somewhere you can read/write data from/to. For the sake of illustration (and don’t use this specific path), let’s say this is /my/datasets/location.

2. Unpack each dataset zip/tar.gz file in /my/datasets/location, so you should have directories like

   /my/dataset/location/G4ABLA3.3
   ... etc ...
   

3. If you are still building/installing Geant4, then add the following to the CMake arguments:

   $ cmake -DGEANT4_INSTALL_DATADIR=/my/dataset/location <otherargs>
   

   This will configure the build/install to look for and use the pre-existing datasets in your chosen location.

   If you have already installed Geant4, then you can point it to this location after installation by setting the environment variable GEANT4_DATA_DIR to, in this example, /my/dataset/location. You don’t need to do this if you set the path through the build/installtion process.

Edit: In regard to the issue with make, this could be due to a bad network connection. There’s usually no easy way to resolve this as it’s highly location/time dependent.