Opened 8 years ago
Closed 8 years ago
#51603 closed defect (fixed)
geant4.10.2 data and geant4make.sh conflict on OSX
Reported by: | fjames-ncat | Owned by: | mojca (Mojca Miklavec) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | geant4.10.2 |
Description
Datatasets for geant4.10.2 have been updated and this has been included in geant4make.sh
export G4RADIOACTIVEDATA="cd $geant4make_root/../../Data/Geant4.10.2/RadioactiveDecay4.3.1 > /dev/null ; pwd
"
export G4ENSDFSTATEDATA="cd $geant4make_root/../../Data/Geant4.10.2/G4ENSDFSTATE1.2.1 > /dev/null ; pwd
"
However, when geant 4.10.2 is installed with macports, the data downloaded contains the old version of these files, RadioactiveDecay4.3 and G4ENSDFSTATE1.2. The new versions are not in the installed dataset.
Therefore, running "source /opt/local/share/Geant4/Geant4-10.2.1/geant4make/geant4make.sh" does not set these globals correctly, and any programs needing those globals fail when one tries to execute then.
Attachments (1)
Change History (5)
comment:1 Changed 8 years ago by mojca (Mojca Miklavec)
Owner: | changed from macports-tickets@… to mojca@… |
---|---|
Port: | geant4.10.2 added |
Version: | 2.3.4 |
comment:2 Changed 8 years ago by mojca (Mojca Miklavec)
Actually, thanks a lot for pointing out this particular problem which I wasn't aware of. I usually only use
/opt/local/libexec/Geant4/Geant4.10.2/geant4data.sh
which (after my local patching that's not committed yet) contains the proper data. I completely forgot to check for other places with potential problems. Let me think a bit about the best possible solution for this.
Changed 8 years ago by mojca (Mojca Miklavec)
Attachment: | geant4.10.2-fix-data.diff added |
---|
A fix for buggy packaging of data files for Geant 4.10.2
comment:4 Changed 8 years ago by mojca (Mojca Miklavec)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Can you please try again after r151271 that switched to version 4.10.02.p02? I believe the commit must have solved the problem, but in case I'm wrong, please let me know.
See http://bugzilla-geant4.kek.jp/show_bug.cgi?id=1849 as the "root of all evil".
I'm annoyed by this, but kept postponing the fix (nobody complained yet). It seems that upstream doesn't plan to fix anything though, so I'll have to implement a workaround.
(PS: when opening a new ticket next time, please add the maintainer to the CC field.)