Linking errors for client_fixture and service_fixture tests

[ros2]

Linking errors for client_fixture and service_fixture tests

[jacquelinekay]

https://github.com/ros2/rcl/blob/master/rcl/test/rcl_add_custom_executable.cmake#L41-Lundefined

It could be that the macro used the build these executables, rcl_add_custom_executables, does not link ${_ARG_APPEND_LIBRARY_DIRS} to the executable, and the missing symbols are passed to the executable through memory tools, which is specified through that argument.

[jacquelinekay]

I'm going to fix up various issues with the cmake infrastructure of rcl tests in an upcoming PR, I'll let you know when it's ready so you can test it locally.

[dirk-thomas]

The build farm is using Docker images with Trusty and therefore g++ 4.8. It should be exactly the same as your version locally.

Therefore I would guess that there must be a difference in:

• either what exactly code you compile (double check that everything is up-to-date and using the right branches)
• or how its build (try a clean build).

[dhood]

I get this even after

vcs pull
rm -r build_isolated install_isolated
src/ament/ament_tools/scripts/ament.py build --build-tests --isolated

Is this outdated? https://github.com/ros2/ros2/blob/ci_scripts/ros2_batch_job/linux_batch/__init__.py#L54 the jobs output that warning.

I did not install connext from debian packages. I'll try that.
Are they still available somewhere so I can update the broken links here https://github.com/ros2/ros2/wiki/Linux-Development-Setup#debian-packages-built-by-osrf (I grabbed them off the buildfarm)

[dhood]

had also done vcs custom --args checkout master by the way

[dirk-thomas]

The latest release from RTI was built with that compiler version and they embed that into the shell file (since they build many different combinations).

There is no public Debian package available since we are not allowed to distribute the package we built for internal use.

[dhood]

update: I changed from the official connext packages (rti_connext_dds-5.2.0-eval-x64Linux3gcc4.8.2.run) to the debian ones and now my linking errors are gone. the debian packages might be using different version of connext

And I will remove that section from wiki entirely since it doesn't sound like it should be there

[dirk-thomas]

The wiki section makes sense for us since it describes what to install if you have access. Therefore I would propose to keep it - eventually improve the note.

[dhood]

ah ok then I'll just explain that it's only for OSRF (assuming that link is still right? I can't access that repo but might just not have the privileges)