|
|
|
Re: Current Trunk version doesn't compile [message #8045 is a reply to message #8039] |
Thu, 12 March 2009 16:53 |
Dmitry Khaneft
Messages: 75 Registered: January 2009
|
continuous participant |
From: 140.181.9*
|
|
I have the same problem with OS Ubuntu8.10 32bit but on my GSI PC with Debian Etch 32bit it was installed without any problem.
By the way if I type make second time it compile successfully but there are errors when I try run sim_emc.C.
Vanniarajan Suyam Jothi wrote on Thu, 12 March 2009 10:53 | Now the MVD part doesn't compile
I get the following Err
[ 43%] Building CXX object mvd/CMakeFiles/Mvd.dir/MvdDAQ/PndMvdConvertApv.o
/home/rugkvi04/vanni/pandaroot/mvd/MvdDAQ/PndMvdConvertApv.cxx: In member
function `std::vector<PndMvdDigiStrip, std::allocator<PndMvdDigiStrip> >
PndMvdConvertApv::Calc(std::vector<PndMvdApvHit,
std::allocator<PndMvdApvHit> >)':
/home/rugkvi04/vanni/pandaroot/mvd/MvdDAQ/PndMvdConvertApv.cxx:156: error: `
SetFeID' undeclared (first use this function)
/home/rugkvi04/vanni/pandaroot/mvd/MvdDAQ/PndMvdConvertApv.cxx:156: error: (Each
undeclared identifier is reported only once for each function it appears
in.)
make[2]: *** [mvd/CMakeFiles/Mvd.dir/MvdDAQ/PndMvdConvertApv.o] Error 1
make[1]: *** [mvd/CMakeFiles/Mvd.dir/all] Error 2
|
[Updated on: Thu, 12 March 2009 16:54] Report message to a moderator
|
|
|
|
|
Re: Current Trunk version doesn't compile [message #8055 is a reply to message #8054] |
Fri, 13 March 2009 12:55 |
Anonymous Poster
|
|
From: *pool.einsundeins.de
|
|
Hi,
I am sorry about this, my compiler didnt mind, but I guess that is why we have this forum...
I changed it to 'throw' which I guess should work with any compiler. BTW, what does everybody think: What is the actual best way to abort the program if something happens that may never happen?
Cheers, Christian
|
|
|
|
|
Re: Current Trunk version doesn't compile [message #8059 is a reply to message #8056] |
Fri, 13 March 2009 13:20 |
Anonymous Poster
|
|
From: *pool.einsundeins.de
|
|
Hi Stefano,
you are right about cases where the fit goes wrong. We dont have a hard abort in that case. The case which came up here, was if someone calls a function which is not implemented. It means that for some track reps, features like extrapolateToPoca dont have to be implemented by all means. However if you want to use the trackRep with hits that need this feature, we want to abort.
Cheers, Christian
|
|
|