Skip to content

Report a bug #2

@JunLi-HIT

Description

@JunLi-HIT

I clone the package in my catkin_ws/src and run
catkin build signal_logger.
A error appears in the terminal as shown below.
Errors << signal_logger_core:make /home/junli/catkin_ws/logs/signal_logger_core/build.make.002.log In file included from /home/junli/catkin_ws/src/signal_logger/signal_logger_core/include/signal_logger_core/BufferInterface.hpp:10:0, from /home/junli/catkin_ws/src/signal_logger/signal_logger_core/include/signal_logger_core/LogElementInterface.hpp:12, from /home/junli/catkin_ws/src/signal_logger/signal_logger_core/include/signal_logger_core/LogElementBase.hpp:11, from /home/junli/catkin_ws/src/signal_logger/signal_logger_core/include/signal_logger_core/SignalLoggerBase.hpp:12, from /home/junli/catkin_ws/src/signal_logger/signal_logger_core/src/SignalLoggerBase.cpp:9: /home/junli/catkin_ws/src/signal_logger/signal_logger_core/include/signal_logger_core/typedefs.hpp:83:8: error: ‘vector’ is not a member of ‘std’ std::vector<T, Eigen::aligned_allocator<T>>, std::vector<T>>::type; ^~~~~~ /home/junli/catkin_ws/src/signal_logger/signal_logger_core/include/signal_logger_core/typedefs.hpp:83:8: error: ‘vector’ is not a member of ‘std’ /home/junli/catkin_ws/src/signal_logger/signal_logger_core/include/signal_logger_core/typedefs.hpp:83:44: error: template argument 2 is invalid std::vector<T, Eigen::aligned_allocator<T>>, std::vector<T>>::type; ^~ /home/junli/catkin_ws/src/signal_logger/signal_logger_core/include/signal_logger_core/typedefs.hpp:83:46: error: expected identifier before ‘,’ token std::vector<T, Eigen::aligned_allocator<T>>, std::vector<T>>::type; ^ In file included from /home/junli/catkin_ws/src/signal_logger/signal_logger_core/include/signal_logger_core/LogElementBase.hpp:12:0, from /home/junli/catkin_ws/src/signal_logger/signal_logger_core/include/signal_logger_core/SignalLoggerBase.hpp:12, from /home/junli/catkin_ws/src/signal_logger/signal_logger_core/src/SignalLoggerBase.cpp:9: /home/junli/catkin_ws/src/signal_logger/signal_logger_core/include/signal_logger_core/Buffer.hpp:150:3: error: ‘vector_type’ does not name a type; did you mean ‘decltype’? vector_type<ValueType_> readNewValues() ^~~~~~~~~~~ decltype In file included from /home/junli/catkin_ws/src/signal_logger/signal_logger_core/include/signal_logger_core/SignalLoggerBase.hpp:12:0, from /home/junli/catkin_ws/src/signal_logger/signal_logger_core/src/SignalLoggerBase.cpp:9: /home/junli/catkin_ws/src/signal_logger/signal_logger_core/include/signal_logger_core/LogElementBase.hpp:131:3: error: ‘vector_type’ does not name a type; did you mean ‘decltype’? vector_type<ValueType_> readNewValues() { return buffer_.readNewValues(); } ^~~~~~~~~~~ decltype In file included from /home/junli/catkin_ws/src/signal_logger/signal_logger_core/src/SignalLoggerBase.cpp:9:0: /home/junli/catkin_ws/src/signal_logger/signal_logger_core/include/signal_logger_core/SignalLoggerBase.hpp:191:3: error: ‘vector_type’ does not name a type; did you mean ‘decltype’? vector_type<ValueType_> readNewValues(const std::string & name) { ^~~~~~~~~~~ decltype /home/junli/catkin_ws/src/signal_logger/signal_logger_core/include/signal_logger_core/SignalLoggerBase.hpp:206:3: error: ‘vector_type’ does not name a type; did you mean ‘decltype’? vector_type<TimestampPair> readNewTimeLogValues(); ^~~~~~~~~~~ decltype /home/junli/catkin_ws/src/signal_logger/signal_logger_core/src/SignalLoggerBase.cpp:540:1: error: ‘vector_type’ does not name a type; did you mean ‘decltype’? vector_type<TimestampPair> SignalLoggerBase::readNewTimeLogValues() { ^~~~~~~~~~~ decltype make[2]: *** [CMakeFiles/signal_logger_core.dir/src/SignalLoggerBase.cpp.o] Error 1 make[1]: *** [CMakeFiles/signal_logger_core.dir/all] Error 2 make: *** [all] Error 2
I add #include <vector> in the typedefs.hpp file, then the package can be compiled successfully.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions