-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linking errors for client_fixture and service_fixture tests #52
Comments
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, |
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. |
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:
|
I get this even after
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. |
had also done |
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. |
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 |
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. |
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) |
Don't require logging users to manually initialise before setting severity
rename message_type_support{_struct}.h
The
service_fixture
andclient_fixture
tests are not linking properly on my machine. The rest work fine.-ldl
is in the linking output, but I think it might be something similar to this issueI'm on Trusty with gcc version 4.8.4. I think the buildfarm has 4.6.3.
I have seen that the
memory_tools
tests are doing something specific withdl
which might be relevant to these tests as well?The text was updated successfully, but these errors were encountered: