[prev in list] [next in list] [prev in thread] [next in thread]
List: orocos-dev
Subject: [Orocos-Dev] [Bug 879] New: Error at compilation depending on logging option choices.
From: paul.chavent () fnac ! net (Chavent Paul)
Date: 2011-06-30 7:40:27
Message-ID: bug-879-4 () http ! bugs ! orocos ! org/
[Download RAW message or body]
http://bugs.orocos.org/show_bug.cgi?id=879
Summary: Error at compilation depending on logging option
choices.
Product: Toolchain
Version: master
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P3
Component: RTT
AssignedTo: orocos-dev at lists.mech.kuleuven.be
ReportedBy: paul.chavent at fnac.net
CC: orocos-dev at lists.mech.kuleuven.be
Estimated Hours: 0.0
In the first case, with these options :
OROBLD_DISABLE_LOGGING OFF
OROSEM_FILE_LOGGING OFF
OROSEM_PRINTF_LOGGING OFF (default)
OROSEM_REMOTE_LOGGING OFF
I got :
rtt/Logger.cpp:298: error: class ?RTT::Logger? does not have any field named
?fileline?
rtt/Logger.cpp:298: error: ?struct RTT::Logger::D? has no member named
?fileline?
In the second case, with these options :
OROBLD_DISABLE_LOGGING ON
OROSEM_FILE_LOGGING ON (default)
OROSEM_PRINTF_LOGGING OFF (default)
OROSEM_REMOTE_LOGGING ON (default)
I got :
rtt/Logger.cpp:587: error: uninitialized reference member
?RTT::Logger::inpguard?
rtt/Logger.cpp:587: error: uninitialized reference member
?RTT::Logger::logline?
rtt/Logger.cpp:587: error: uninitialized reference member
?RTT::Logger::fileline?
and some unresolved symbols on "Logger& Logger::operator<<( const char* t )".
So this patch should avoid those error.
I wonder if we can disable logging if file and printf and remote logging are
disabled ?
--
Configure bugmail: http://bugs.orocos.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic