SCons build error: undefined reference to `typeinfo for THcFormula' about hcana HOT 7 CLOSED

THcFormula.cxx was not added into the SConscript.py script in the ~/hcana/src directory ... I added it and have committed that change, but have not done a pull request yet (or, more properly, I am still working on a couple of other things). In particular, I am working on testing changes to hcana that would unbundle SCons, and just use the system version, like is done for the Hall A analyzer.

I must admit that I am a bit confused right now as to what "version" of podd is being tagged in hcana. I had thought that it was supposed to be Release-150, which should have the unbundling of SCons in it, yes? But I think maybe Steve has to change the specific commit that is "pointed" to in hcana ...

Best,
E.

from hcana.

Steve has merged this pull request now ... so I think that this issue can be closed.

from hcana.

BTW, I just did a separate pull request that includes a change to the README.md file which now gives updated SCons compilation instructions. It should be updated on the Wiki as well. I am not sure if I have permissions to updated the Wiki.

from hcana.

OK, I updated the Hall C wiki (ROOT Analyzer/Compiling page), although there was nothing there about SCons, in fact. Ole, where on the wiki did you find the instructions for scons that you noted above?

from hcana.

I followed the instructions on

https://hallcweb.jlab.org/wiki/index.php/Analyzer/Compiling

Towards the bottom, it says:

"To use SCons, type:

scons
"
When I do that, I get:
scons: Reading SConscript files ...
!!! You should be using the local version of SCons, invoked with:
!!! ./podd/scons/scons.py
SCons 4.9.9 or greater required, but you have SCons 2.1.0

So I invoke scons as instructed with:
./podd/scons/scons.py

which eventually gives the error message about THcFormula.cxx. I added the parameters "debug=1 -j4" to the scons command because that's what I usually use, but the error occurs with or without the parameters.

That said, all of the above problems have gone away after I updated to the latest upstream, so you can close this issue now.

from hcana.

I don't see any way for me to close this issue (by hand) ... I guess maybe I don't have permissions to close issues on this repository?

from hcana.

Works for me now. Closing this following the discussion.

from hcana.