Closed villaa closed 2 years ago
I have tried to roll back the c++ standard, trying -std=c++98
which failed to compile, and -std=c++11
which compiled but also gave errors.
I am now trying to rollback my version of ROOT
, which is apparently not easy with brew
. Apparently you used to be able to just directly use a URL from the brew repository of an old commit. I tried that, and it failed b/c this is no longer allowed.
There are actually now what seem to be better ways to do this, so I am trying the method here in the first answer.
Note that this is all supposed to be done in a terminal (any terminal) and it seems like the TAP
variable is largely arbitrary. I used:
(base) Anthonys-MacBook-Pro:~ villaa$ TAP="villano-lab/homebrew-old"
(base) Anthonys-MacBook-Pro:~ villaa$ MODULE="root"
(base) Anthonys-MacBook-Pro:~ villaa$ VERS="6.22.08"
which might be working??
BTW the version I used to link to was 6.22.08 the direct URL is in this link.
Installed the older version of ROOT
and got it working by doing source /usr/local/Cellar/root\@6.22.08/6.22.08_2/bin/thisroot.sh
version 6.22.08
actually also forces the -std=c=++17
flag:
(base) Anthonys-MacBook-Pro:nrCascadeSim villaa$ root-config --cflags --glibs
-stdlib=libc++ -pthread -std=c++17 -m64 -I/usr/local/Cellar/root@6.22.08/6.22.08_2/include/root -L/usr/local/Cellar/root@6.22.08/6.22.08_2/lib/root -lGui -lCore -lImt -lRIO -lNet -lHist -lGraf -lGraf3d -lGpad -lROOTVecOps -lTree -lTreePlayer -lRint -lPostscript -lMatrix -lPhysics -lMathCore -lThread -lMultiProc -lROOTDataFrame -stdlib=libc++ -lpthread -lm -ldl
So, I guess I have to go back even further to test a previous version than c++17
So I made this post to the ROOT
forum to try to figure out how far in versions I have to go back to get something compatible with c++14
. It's hard to tell from the ROOT
release pages.
See issue #10 for some related stuff about ROOT
installs.
Note: found out that ROOT 6.16/00 uses C++14
Addressed by PR #61 -- we decided to support ROOT versions 6.20.00 through 6.24.06.
I often (but not always!?) get strange errors when running with the setup (although everything compiles thanks to the PR #28).
The errors look like:
It's clear that something is going wrong with reading the file because of the whack values for the neutron separation energy in the first record.