YARP Installation Troubleshooting Tips

From Wiki for iCub and Friends
Jump to: navigation, search

YARP test fails

(from Giorgio after Paul's explanation)

If the 'make test' gets stuck (hanging indefinitely) please check that all yarp processes are terminated before running the test. The test uses some tcp/ip ports indiscriminately and this goes into conflict if other yarp processes try to do the same. The 'make test' is meant for testing and as such it should only be used alone.


(from Gianluca)

Symptom: GUI would not compile.

The first problem was with glib-2.0. On my Suse box, I have installed both gtk+ 1.0 and gtk+ 2.0... but there is only ONE file glibconfig.h in /opt/gnome/include. The /opt/gnome/include/glibconfig.h is a symbolic link to /opt/gnome/lib/glib/include/glibconfig.h but if you compiling a gtk2 application you have to change that symbolin link to /opt/gnome/lib/glib-2.0/include/glibconfig.h

 OLD:   lrwxrwxrwx  1 root root 36 Jul  7 14:38 glibconfig.h -> ../lib/glib/include/glibconfig.h
 NEW:  lrwxrwxrwx  1 root root 36 Jul  7 14:38 glibconfig.h -> ../lib/glib-2.0/include/glibconfig.h

The second problem was about linking directories. For some reasons obscure to me, the linker doesn't look for libraries into default directories... so there are some error about missing libraries. I addes this line to CMakeList.txt ... and all things compiled and linked well  :-)

 *LINK_DIRECTORIES*(/opt/gnome/lib /usr/X11R6/lib)

Private Installs

(from Anthony "Jek-Ender")

I've just gotten YARPed on my Linux box without problem :-)

Here are some basic but usefull tips for others installing everything in ~/local without being root.

Don't forget to set the env var LD_LIBRARY_PATH and LD_RUN_PATH -- so that your ACE and YARP installation are searchable for dynamic libraries -- before building and running yarp. On my system I added this to my ~/.zshrc : Code:

 export LD_LIBRARY_PATH=~/local/lib
 export LD_RUN_PATH=~/local/lib

Beware On a Mac the analog of LD_LIBRARY_PATH is usualy DYLD_LIBRARY_PATH, but setting it will break any thing launched from the command line (don't ask why... ). You should set DYLD_FALLBACK_LIBRARY_PATH instead !

glibc detected corrupted double-linked

(by dimitri) I had this error on my good old slackware, with glibc-2.3.6

The error is not shown anymore and the test goes well if you set "export MALLOC_CHECK_=0"

(response from paulfitz) I ran valgrind on the library and found a bug that could have caused this - it is now fixed in CVS. If this problem recurs please report it to me.