Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing headers when installed #1

Closed
brettviren opened this issue Nov 8, 2017 · 1 comment
Closed

Missing headers when installed #1

brettviren opened this issue Nov 8, 2017 · 1 comment

Comments

@brettviren
Copy link
Contributor

Running edep-sim from an in-source build of master seems to allow an error free run.

Running it from an installed location leads to errors due to missing headers. The installation I'm testing is created using spack install edepsim@master using the Spack fork in my GitHub area. But, I think this problem is unrelated to Spack per se but rather due to running from an installation location other than where the build occurred.

Here is the error output:

Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState:
   Missing FileEntry for /opt/spack/spack/var/spack/stage/edepsim-master-aizbsjr3dc2qyhbbk6cd66q6qckgixvn/edep-sim/src/TG4PrimaryVertex.h
   requested to autoload type TG4PrimaryVertex
Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState:
   Missing FileEntry for /opt/spack/spack/var/spack/stage/edepsim-master-aizbsjr3dc2qyhbbk6cd66q6qckgixvn/edep-sim/src/TG4PrimaryVertex.h
   requested to autoload type TG4PrimaryParticle
Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState:
   Missing FileEntry for /opt/spack/spack/var/spack/stage/edepsim-master-aizbsjr3dc2qyhbbk6cd66q6qckgixvn/edep-sim/src/TG4Trajectory.h
   requested to autoload type TG4Trajectory
Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState:
   Missing FileEntry for /opt/spack/spack/var/spack/stage/edepsim-master-aizbsjr3dc2qyhbbk6cd66q6qckgixvn/edep-sim/src/TG4Trajectory.h
   requested to autoload type TG4TrajectoryPoint
Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState:
   Missing FileEntry for /opt/spack/spack/var/spack/stage/edepsim-master-aizbsjr3dc2qyhbbk6cd66q6qckgixvn/edep-sim/src/TG4HitSegment.h
   requested to autoload type TG4HitSegment
Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState:
   Missing FileEntry for /opt/spack/spack/var/spack/stage/edepsim-master-aizbsjr3dc2qyhbbk6cd66q6qckgixvn/edep-sim/src/TG4Event.h
   requested to autoload type TG4Event
libedepsim dictionary payload:46:10: fatal error: '/opt/spack/spack/var/spack/stage/edepsim-master-aizbsjr3dc2qyhbbk6cd66q6qckgixvn/edep-sim/src/TG4PrimaryVertex.h' file not found
#include "/opt/spack/spack/var/spack/stage/edepsim-master-aizbsjr3dc2qyhbbk6cd66q6qckgixvn/edep-sim/src/TG4PrimaryVertex.h"
         ^
Error in <TInterpreter::AutoParse>: Error parsing payload code for class TG4HitSegment with content:

The job does actually complete and a quick check of the output ROOT file shows no immediate problems but I've yet to get edep-disp (which also gives errors like the above) to show meaningful results on the file.

That path referenced in the error is a temporary build area and doesn't exist after installation. It looks like something in the build is baking-in this path.

FWIW, setting ROOT_INCLUDE_PATH to point at directories in a copy of edep-sim source doesn't help.

@brettviren
Copy link
Contributor Author

Even with -inlineInputHeader as added in #2, one needs to set ROOT_INCLUDE_PATH (to in-source location of includes for now) or else edep-sim gives complaints like:

Error in <TClass::LoadClassInfo>: no interpreter information for class TG4TrajectoryPoint is available even though it has a TClass initialization routine.
libedepsim dictionary payload:344:10: fatal error: 'TG4PrimaryVertex.h' file not found
#include "TG4PrimaryVertex.h"
         ^
Error in <TInterpreter::AutoParse>: Error parsing payload code for class TG4Trajectory with content:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant