Skip to content
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

WBToolbox fails to compile in a clean installation #418

Closed
S-Dafarra opened this issue Jun 4, 2020 · 8 comments
Closed

WBToolbox fails to compile in a clean installation #418

S-Dafarra opened this issue Jun 4, 2020 · 8 comments

Comments

@S-Dafarra
Copy link
Collaborator

The error is

[ 44%] Building CXX object toolbox/library/CMakeFiles/WBToolbox.dir/src/SimulatorSynchronizer.cpp.o
make[5]: *** No rule to make target '/usr/local/src/robot/robotology-superbuild/build/install/lib/libqpOASES.so', needed by 'lib/libWBToolbox.so'.  Stop.
CMakeFiles/Makefile2:254: recipe for target 'toolbox/library/CMakeFiles/WBToolbox.dir/all' failed
make[4]: *** [toolbox/library/CMakeFiles/WBToolbox.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make[3]: *** [all] Error 2
CMakeFiles/WBToolbox.dir/build.make:110: recipe for target 'robotology/WBToolbox/CMakeFiles/YCMStamp/WBToolbox-build' failed
make[2]: *** [robotology/WBToolbox/CMakeFiles/YCMStamp/WBToolbox-build] Error 2
CMakeFiles/Makefile2:2764: recipe for target 'CMakeFiles/WBToolbox.dir/all' failed
make[1]: *** [CMakeFiles/WBToolbox.dir/all] Error 2
Makefile:94: recipe for target 'all' failed
make: *** [all] Error 2

It is necessary to compile qpOases first, install it , and then it works.

A simple way to reproduce this is to delete the install folder and try to recompile.

@traversaro
Copy link
Member

On which OS are you experiencing this problem?

@traversaro
Copy link
Member

One thing that I don't understand is how you were able to configure WB-Toolbox if qpOASES was not installed.

@S-Dafarra
Copy link
Collaborator Author

On which OS are you experiencing this problem?

Sorry, Ubuntu 18.04. It happened when trying to update the iCub head and the laptop. In both cases I was using the master version of the robotology superbuild. The thing I thought it was fishy is that it should not try to compile WBToolbox if qpOases was not built before right?

@traversaro
Copy link
Member

The superbuild is up-to-dated with the latest commit?

I think the following happened:

  • For some reason, the qpOASES of the superbuild was found by the superbuild itself (you can check this by inspecting the CMakeCache.txt of the superbuild), this should be avoided in the future as soon as the next YCM version is released thanks to Set YCM option YCM_DISABLE_SYSTEM_PACKAGES to ON #389 .
  • On the top of that, somebody canceled the installed file /usr/local/src/robot/robotology-superbuild/build/install/lib/libqpOASES.so

Did you experience this in a clean build?

@S-Dafarra
Copy link
Collaborator Author

The superbuild is up-to-dated with the latest commit?

Yes, 1db39df

On the top of that, somebody canceled the installed file /usr/local/src/robot/robotology-superbuild/build/install/lib/libqpOASES.so

I did that 😁 Actually, I did it because at the beginning it did not seem to compile yarp correctly.

@traversaro
Copy link
Member

I think you should check your CMakeCache.txt (of the superbuild) and remove any reference to qpOASES, that should ensure that qpOASES is configured and installed before the WB-Toolbox.

@S-Dafarra
Copy link
Collaborator Author

Ok great! Anyways, this was just to notify. By going into the qpOases build folder and install it again fixes the problem.

@traversaro
Copy link
Member

traversaro commented Jun 4, 2020

If qpOASES is not compiled every-time that WB-Toolbox is compiled, then if qpOASES is updated you will not get the updated version of qpOASES, leading to quite subtle behaviors . In any case, I tried to reproduce the system on a clean build of robotology-superbuild on Ubuntu 18.04 and it does not appear, so I would think that the problem is due to some environment condition such as the one previously mentinoned. Unless you plan to investigate the problem further, I would close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants