search

LArbys / larlitecv

Analysis processor framework for working with LArLite and LArCV data
1 stars 0 forks source link

Chris linker libraries error #21

Closed barnchri closed 7 years ago

barnchri commented 7 years ago

/home/barnchri/Clean_Tagger_for_Flash_Match_Integration/dllee_unified/larlitecv/build/lib/liblarlitecv.so: undefined reference to larlitecv::GeneralFlashMatchAlgo::generate_single_opflash_vector_for_event(std::vector<larlite::event_opflash*, std::allocator<larlite::event_opflash*> >)' /home/barnchri/Clean_Tagger_for_Flash_Match_Integration/dllee_unified/larlitecv/build/lib/liblarlitecv.so: undefined reference tolarlitecv::GeneralFlashMatchAlgo::generate_chi2_in_track_flash_comparison(flashana::QCluster_t, larlite::opflash, int)' /home/barnchri/Clean_Tagger_for_Flash_Match_Integration/dllee_unified/larlitecv/build/lib/liblarlitecv.so: undefined reference to larlitecv::GeneralFlashMatchAlgo::ExpandQClusterStartingWithLarliteTrack(flashana::QCluster_t, larlite::track const&, double, bool, bool)' collect2: error: ld returned 1 exit status make[1]: *** [run_tagger] Error 1 make[1]: Leaving directory/home/barnchri/Clean_Tagger_for_Flash_Match_Integration/dllee_unified/larlitecv/app/TaggerCROI/bin' make: *** [bin] Error 2

^ This error comes from the 'run_tagger.cxx' executable in the 'larlitecv/app/TaggerCROI/bin' directory. The GNUmakefile has to be modified somehow.

vgenty commented 7 years ago

i updated the makefile to build your new module, please pull on chris_linker_libraries_error

and take a look. here is the commit: https://github.com/LArbys/larlitecv/commit/165170423a3181ec6e1530533ac2e3796e58a0d6

twongjirad commented 7 years ago

I failed to pull and conflicted with @vgenty 's edits -- but did the same thing (sorry Vic!). There were also some pointer operator errors I got. Don't know if Vic did as well. It builds. BUT I did not test if it actually ran and worked. I leave that to @barnchri to do. Once it works, then we should merge the branches. (though the head of the tagger is now on tmw_tagger_charge_checks (or something like that). We can worry about that later.