[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [certi-dev] trouble linking with libFedTime with gcc 5.2.1

From: Eric Noulard
Subject: Re: [certi-dev] trouble linking with libFedTime with gcc 5.2.1
Date: Tue, 17 Nov 2015 06:17:25 +0100

2015-11-16 18:43 GMT+01:00 Mattias Helsing <address@hidden>:

I'm having trouble linking even testapps that are part of CERTI. I'm
building on ubuntu 15.10 using GCC 5.2.1. I suspect there is some
circular dependency but haven't yet investigated further. I get the

The circular ref issue is a known problem but it has been handled
(not a definitive fix though) long time ago.

Which version of CERTI are you trying to build?

Could you try to change version of compiler,
see recent thread about that issue here:

We need a real fix for this circular ref issue but I have not time to work on this for now.

Scanning dependencies of target TestFedTime
make[2]: Leaving directory '/home/helsing/local/src/CERTI/build-release'
make[2]: Entering directory '/home/helsing/local/src/CERTI/build-release'
[ 66%] Building CXX object
[ 66%] Linking CXX executable TestFedTime
libFedTime.so.1.0.0: undefined reference to `typeinfo for RTI::Exception'
collect2: error: ld returned 1 exit status
libRTI/hla-1_3/CMakeFiles/TestFedTime.dir/build.make:100: recipe for
target 'libRTI/hla-1_3/TestFedTime' failed
make[2]: *** [libRTI/hla-1_3/TestFedTime] Error 1
make[2]: Leaving directory '/home/helsing/local/src/CERTI/build-release'
CMakeFiles/Makefile2:776: recipe for target
'libRTI/hla-1_3/CMakeFiles/TestFedTime.dir/all' failed
make[1]: *** [libRTI/hla-1_3/CMakeFiles/TestFedTime.dir/all] Error 2
make[1]: Leaving directory '/home/helsing/local/src/CERTI/build-release'
Makefile:160: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/home/helsing/local/src/CERTI/build-release'
address@hidden:~/local/src/CERTI$ make -C build-release/ edit_cache
make: Entering directory '/home/helsing/local/src/CERTI/build-release'
Running CMake cache editor...

Is this something that you are aware about or even have a fix for?
Should I try an experimental build to the Dashboard?

Yes see:

and reference therein:

CERTI-Devel mailing list


reply via email to

[Prev in Thread] Current Thread [Next in Thread]