hejb
November 24, 2010, 10:18pm
1
Hello,
I just updated to the revision 36918 and got the following problem during compilation on an SLC5 machine. Is this problem already known? Could you please fix it?
Thanks a lot.
==> cint/cint/stl/valarray.so done
mv cint/cint/stl/valarray.so cint/cint/stl/valarray.dll
cint/cint/main/cint_tmp
-w1 -zstdcxxfunc -ncint/cint/lib/G__cpp_stdcxxfunc.cxx
-D__MAKECINT__ -DG__MAKECINT -Icint/cint/lib/
-c-1 -A -Z0 cint/cint/lib/stdstrct/stdcxxfunc.h
bin/rmkdepend -R -fcint/cint/lib/G__cpp_stdcxxfunc.d -Y -w 1000 –
-pipe -m64 -Wshadow -Wall -W -Woverloaded-virtual -fPIC -Iinclude -pthread -D__cplusplus -Icint/cint/lib/prec_stl
-Icint/cint/stl -I/exp/LHCb/software/ROOT/svntrunk/cint/cint/inc – cint/cint/lib/G__cpp_stdcxxfunc.cxx
g++ -pipe -m64 -Wshadow -Wall -W -Woverloaded-virtual -fPIC -Iinclude -pthread -I. -I/exp/LHCb/software/ROOT/svntrunk/cint/cint/inc -o cint/cint/lib/G__cpp_stdcxxfunc.o -c cint/cint/lib/G__cpp_stdcxxfunc.cxx
g++ -shared -Wl,-soname,stdcxxfunc.so -m64 -O2 -o cint/cint/include/stdcxxfunc.so cint/cint/lib/G__cpp_stdcxxfunc.o
==> cint/cint/include/stdcxxfunc.so done
mv cint/cint/include/stdcxxfunc.so cint/cint/include/stdcxxfunc.dll
bin/rmkdepend -R -fcint/cint/lib/dll_stl/rootcint_complex.d -Y -w 1000 – -pipe -m64 -Wall -W -Woverloaded-virtual -fPIC -Iinclude -DG__REGEXP -DG__UNIX -DG__SHAREDLIB -DG__OSFDLL -DG__ROOT -DG__REDIRECTIO -DG__STD_EXCEPTION -DG__64BIT -DG__HAVE_CONFIG -DG__NOMAKEINFO -DG__CINTBODY -I/exp/LHCb/software/ROOT/svntrunk/cint/cint/inc -I/exp/LHCb/software/ROOT/svntrunk/cint/cint/src -I/exp/LHCb/software/ROOT/svntrunk/cint/cint/src/dict -pthread -I. -I. -D__cplusplus – /exp/LHCb/software/ROOT/svntrunk/cint/cint/lib/dll_stl/rootcint_complex.cxx
g++ -O2 -pipe -m64 -Wall -W -Woverloaded-virtual -fPIC -Iinclude -DG__REGEXP -DG__UNIX -DG__SHAREDLIB -DG__OSFDLL -DG__ROOT -DG__REDIRECTIO -DG__STD_EXCEPTION -DG__64BIT -DG__HAVE_CONFIG -DG__NOMAKEINFO -DG__CINTBODY -I/exp/LHCb/software/ROOT/svntrunk/cint/cint/inc -I/exp/LHCb/software/ROOT/svntrunk/cint/cint/src -I/exp/LHCb/software/ROOT/svntrunk/cint/cint/src/dict -pthread -I. -I. -o cint/cint/lib/dll_stl/rootcint_complex.o -c /exp/LHCb/software/ROOT/svntrunk/cint/cint/lib/dll_stl/rootcint_complex.cxx
/exp/LHCb/software/ROOT/svntrunk/cint/cint/lib/dll_stl/rootcint_complex.cxx: In function �ROOT::TGenericClassInfo* ROOT::GenerateInitInstanceLocal(const std::complex)�:
/exp/LHCb/software/ROOT/svntrunk/cint/cint/lib/dll_stl/rootcint_complex.cxx:197: error: invalid conversion from �void ( )(void*, TMemberInspector&, char*)� to �void ()(void , TMemberInspector&)
/exp/LHCb/software/ROOT/svntrunk/cint/cint/lib/dll_stl/rootcint_complex.cxx:197: error: initializing argument 6 of �ROOT::TGenericClassInfo::TGenericClassInfo(const char*, const char*, Int_t, const std::type_info&, const ROOT::TInitBehavior*, void ()(void , TMemberInspector&), void ()(), TVirtualIsAProxy , Int_t, Int_t)
/exp/LHCb/software/ROOT/svntrunk/cint/cint/lib/dll_stl/rootcint_complex.cxx: In function �ROOT::TGenericClassInfo* ROOT::GenerateInitInstanceLocal(const std::complex)�:
/exp/LHCb/software/ROOT/svntrunk/cint/cint/lib/dll_stl/rootcint_complex.cxx:295: error: invalid conversion from �void ( )(void*, TMemberInspector&, char*)� to �void ()(void , TMemberInspector&)
/exp/LHCb/software/ROOT/svntrunk/cint/cint/lib/dll_stl/rootcint_complex.cxx:295: error: initializing argument 6 of �ROOT::TGenericClassInfo::TGenericClassInfo(const char*, const char*, Int_t, const std::type_info&, const ROOT::TInitBehavior*, void ()(void , TMemberInspector&), void ()(), TVirtualIsAProxy , Int_t, Int_t)
make: *** [cint/cint/lib/dll_stl/rootcint_complex.o] Error 1
rdm
November 25, 2010, 11:08am
2
Hi,
alas, with the trunk 36929 I cannot reproduce this issue on my SLC5 64-bit machine.
Cheers, Fons.
hejb
November 25, 2010, 11:23am
3
Yes, now the compilation is ok after updating to 36933. And I had no problem in compiling 36917 (it was quicker than on our cluster) on my laptop (Ubuntu 10.10, 64 bit). It seems there is no fix for that file. So I don’t know what happened. Maybe something was wrong during updating. Anyway, since it is working now, no worry at all. Thanks.