Package Details: geant4 11.3.0-1

Git Clone URL: https://aur.archlinux.org/geant4.git (read-only, click to copy)
Package Base: geant4
Description: A simulation toolkit for particle physics interactions.
Upstream URL: http://geant4.cern.ch/
Keywords: matter montecarlo radiation transport
Licenses: custom: http://geant4.cern.ch/license/
Conflicts: geant4_devel
Submitter: Eothred
Maintainer: donpicoro
Last Packager: donpicoro
Votes: 19
Popularity: 0.000099
First Submitted: 2010-04-08 08:54 (UTC)
Last Updated: 2024-12-08 19:13 (UTC)

Dependencies (29)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 15 Next › Last »

donpicoro commented on 2022-03-09 13:44 (UTC)

@f3fora: my bad... my emacs-pkgbuild-mode made a number on me. Now it's fixed.

f3fora commented on 2022-03-09 10:53 (UTC) (edited on 2022-03-09 11:06 (UTC) by f3fora) 

==> Making package: geant4 11.0.1-1 (Wed 09 Mar 2022 11:49:30)
==> Retrieving sources...
  -> Found geant4-v11.0.1.tar.gz
  -> Found geant4.install
==> Validating source files with md5sums...
    geant4-v11.0.1.tar.gz ... FAILED
    geant4.install ... Passed
==> ERROR: One or more files did not pass the validity check!
error: failed to download sources for 'geant4-11.0.1-1':
error: packages failed to build: geant4-11.0.1-1

Fix:

md5sum geant4-v11.0.1.tar.gz
598d6d3489214a1e7e3c4c02084b7faa  geant4-v11.0.1.tar.gz

donpicoro commented on 2022-01-31 10:12 (UTC)

Hello again,

I guess you are compiling it "normally" and not inside a 'chroot' (https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot).

As soon as I try to compile it I run into a dependency black hole similar to what I reported before.

At to moment I do not have the time to keep looking into this issue, in particular for this driver that you report is not functional yet.

I will keep this in the back of my head and give it a go every once in a while.

Cheers,

gipert commented on 2022-01-30 20:58 (UTC)

With this PKGBUILD I manage to compile it: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=geant4-debug. The error you get is because VTK needs the Java headers. Let me know whether the driver is then actually usable for you, it wasn't for me.

Another feature I would really like to use is HDF5 support for object persistency. The problem is that multithreaded G4 requires the HDF5 C library to be compiled in thread-safe mode, and this is not the case with the Arch package (there are compatibility issues with other Arch packages, as far as I understand).

A workaround would be to compile a private version of the HDF5 library, but it would require quite a bit of PKGBUILD development, I guess.

Good luck!

donpicoro commented on 2022-01-30 19:31 (UTC)

Dear @gipert,

how did you manage to get the Vtk support working? As soon as I added -DGEANT4_USE_VTK=ON I ended up needing a ton of extra dependencies only to get it to fail at the end.

This are the dependencies: 

         'vtk'
         'openmpi'
         'python-mpi4py'
         'ospray'
         'openvr'
         'postgresql-libs'
         'pdal'
         'libogg'
         'libtheora'
         'liblas'
         'libharu'
         'adios2'
         'ffmpeg'
         'gl2ps'
         'cgns'
         'qt5-quickcontrols'
         'glew'
         'eigen'
         'fmt'
         'utf8cpp'

and in the end it failed anyway

CMake Error in source/CMakeLists.txt:
  Imported target "VTK::Java" includes non-existent path

    "/usr/lib/jvm/default/include"

gipert commented on 2022-01-25 16:44 (UTC)

Forget about my last comment. I tested the new driver a bit and found it quite unstable, at least on Arch. We should maybe reconsider it once the feature is more mature.

gipert commented on 2022-01-13 15:57 (UTC)

Hello @donpicoro, thanks a lot for keeping the package up to date. What about supporting the VTK visualization driver?

donpicoro commented on 2021-07-13 14:57 (UTC)

Hello once more @gipert:

it turned out much easier than I thought. I do not want to bump the release to avoid unnecessary re-compilations. However I already tested in my machine and it works for me and they should be there when the next release or patch comes out.

1) The std17: It juts works, so I just changed it to GEANT4_BUILD_CXXSTD=17

2) ldconfig : it turns out that the geant.[c]sh was mainly setting some Xerces, etc... libraries which they all live, along with the new G4 ones, under /usr/lib. It turns out that /usr/lib is actually included by default by ldconfig. So... there is nothing to add there even ;-)

gipert commented on 2021-07-13 13:24 (UTC)

Hi @donpicoro. Indeed the right way is to add a config file below /etc/ld.so.conf.d.

As for the standard, I'm only suggesting this because it's a general practice in Arch Linux packages to compile the C++ sources with recent standards (see e.g. ROOT). Not a big issue just a remark.

« First ‹ Previous 1 2 3 4 5 6 7 .. 15 Next › Last »