-
Notifications
You must be signed in to change notification settings - Fork 48
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
Undefinded problems encountered during the build process #1168
Comments
Hi @SSSSamZhu, which base docker image are you using? Thanks. |
Hi @traversaro |
Hi @SSSSamZhu, |
Hi @traversaro, |
Hi @SSSSamZhu, sorry but your original message started with:
Anyhow, if you are not using Docker, can you report:
|
Hi @traversaro,
looking forward to your reply. |
Hi @SSSSamZhu, as mentioned before, can you:
Thanks. |
Hi @traversaro,
Maybe you need this files ,error.log |
Hi @SSSSamZhu, with:
I meant type the |
Hi @traversaro,
|
From the output, and the fact that your username is prefixed by
|
Morning @traversaro,
Looking forward to your reply |
Probably To check this, can you please:
Thanks |
Hi @traversaro,
Compared with the previous increase of environment variables, there are several reduced.I don't have an effective solution to this situation.But the environment variables you mentioned above should have been introduced when yarp and icub-main source files were configured
This is the contents of the environment variable configuration file
Thank you. |
The For your specific linking problem, I still does not understand what is going on, as additional info can you provide:
Sorry for asking so much info, I am quite confused as we continuously test this in CI and never saw something similar. The only difference between your case and the CI is that in your case you have ROS enabled, so if you want to try it could make sense to comment out from the Another workaround you may try is to uninstall the |
Hi @traversaro,
3.4. Thank you. |
Hi @SSSSamZhu, perhaps I am missing something but the |
Hi @traversaro, |
I meant running:
|
Thanks, as I mentioned before, the problem is always the same, there is still cross-talking between apt libraries and conda libraries. If you check your environment, you will see that even if you deactivated the environment, you still have If you are not using |
Hi @traveraro,
CMakeCache.txt and compile_commands.json
In conclusion, thank you very much for your patience |
You can try, as long as you do not source the
Did you remove your build directory and created a new one after you removed |
Hi @traveraro,
We have referred to this issue and it is useful to some extent.
In conclusion, thank you very much for your patience. |
spdlog problemBeside the workaround you found, another fix is to just compiled spdlog as a shared library. However, why do you have a custom install of spdlog in fatal: unsafe repository error (is owned by someone else)This is a problem that I never saw, I need to think about it. |
Did you added a symbolic link |
As you may have noticed, the operation of installing manually in
Then, make sure that
Notice that should be already done by the For what regards the strange error related to YARP_telemetry, did you try to execute the workaround the error is suggesting, i.e.:
? |
Hello @traveraro,
After I repeat make a few times, the
4.Finally, delete the source code package |
Good to know @SSSSamZhu . For your own knoledge, for the uninstall the If everything works, feel free to close the issue. |
That would be ideal, so you avoid the risk of mixing different versions of libraries that may not be ABI-compatible.
You can try to remove any reference to manually build YARP, icub, etc etc from environment variables, but my suggestion is just to remove every library that you manually built, and re-run a clean build of the superbuild just to be sure. If you installed this libraries in a global location like |
By the way, I noticed that the location of the custom built iCub is |
The device's user name was changed once, from Roboverse to icub. I modified what I could find. But not quite.
Thanks, it works. It seems that the two installation methods are in conflict, and at first I was just going to use Conda to build in a separate environment. Finally, thank you again |
Great! |
If there is no |
Morning @traveraro,
|
Indeed, it seems that there are no strange env variable. However, it is still possible to accidentally installed a YARP in
|
|
Nothing strange here, I wonder if the segmentation fault is caused by something else and not by some incompatibility with a previously compiled YARP library. |
Hi @traveraro,
In fact, I confirm that YARP has been compiled and installed separately. I remember that yarpmanager could be run directly at that time .Although YARP directly seen in the terminal is version 3.7 under Superbuild, so I think that YARP compiled separately before (version 3.6) affects YARP under Superbuild.
Could it be that we're missing something that needs to be configured? |
Ok, in that case can you open a terminal without sourcing the |
The original 3.6.0 version of YARP doesn't seem to open anymore ,So far all points to superbuild YARP .
|
Hi @traveraro,
|
It seems that the installation of YARP in |
This is what I intended to do at first, but when I recompiled the source file, he reported this error again. So I can't compile.
|
Are you sure you have space in the disk? |
Then I am not sure what could be the problem, as the superbuild instead works correctly. Are you sure that you have a clean environment, i.e. you do not source You could also try to use a different build directory, or clone the yarp repo completly in another location. |
You are right, because I already executed these commands when I compiled YARP separately from the root directory. Thank you for your warning.
Unfortunately, it doesn't seem to solve the superbuild problem completely. The terminal reported the following error .
|
For some reason the system installed YARP installed its cmake files in
After this, you can check if your
If nothing is printed, we are good. Otherwise, probably the files listed will need to be removed manually as well. |
Hi @traveraro,
|
Hi @SSSSamZhu, can you open a separate issue in https://github.com/robotology/community for this problem? I think that we debugged enough problems in this issue, and for clarity it is good to have an issue for each problem, thanks! |
ok, I will close this issue. Thanks! |
I'm trying to build the v2022.5.0 tag of the superbuild in a clean docker image with the following command:
ROBOTOLOGY_ENABLE_DYNAMICS = ON
ROBOTOLOGY_ENABLE_DYNAMICS _FULL = ON
Error
looking forward to your reply.
The text was updated successfully, but these errors were encountered: