undefined symbol: vit_api_get_version
Tried building & running monado-service with libbasalt with recent versions today on Debian Sid. Building went through fine (after the manual edit for #11), however when trying to run monado-service it fails to me like this now:
$ sudo nice -n -10 su -c "XRT_DEBUG_GUI=0 XRT_COMPOSITOR_COMPUTE=1 ~/.local/bin/monado-service" linus > ~/dev-priv/vr/monado-basalt-error.log 2> ~/dev-priv/vr/monado-basalt-error.log
$ cat ~/dev-priv/vr/monado-basalt-error.log
INFO [ipc_server_main] Monado(XRT) by Collabora et al 'v24.0.0-97-gecaab0f63e49' starting up...
INFO [wmr_read_config] Manufacturer: HP Inc.
INFO [wmr_read_config] Device: VR3000-0XX
INFO [wmr_read_config] Serial: 8CC107Z5SM
INFO [wmr_read_config] UID: {26412B58-5143-56AD-8222-A3E26B87E5FB}
INFO [wmr_read_config] Name: HP Reverb Virtual Reality Headset G2
INFO [wmr_read_config] Revision: RevB.M.J
INFO [wmr_read_config] Revision Date: 2021-02-22
INFO [wmr_hmd_create] Found WMR headset type: HP Reverb G2
INFO [wmr_hmd_create] FoV eye 0 angles left -0.906347 right 0.724723 down -0.808741 up 0.813367
INFO [wmr_hmd_create] Render texture range -1.276718, -1.047811 to 0.885459, 1.057563
INFO [wmr_hmd_create] FoV eye 1 angles left -0.724211 right 0.904758 down -0.808154 up 0.811717
INFO [wmr_hmd_create] Render texture range -0.884545, -1.046579 to 1.272547, 1.054073
INFO [wmr_hmd_activate_reverb] Sent activation report.
INFO [wmr_hmd_activate_reverb] Sleep until the HMD display is powered up, so the available displays can be enumerated by the host system.
INFO [t_slam_create] Loading VIT system library from VIT_SYSTEM_LIBRARY_PATH='libbasalt.so'
ERROR [vit_get_proc] Failed to load symbol /home/linus/dev-priv/vr/basalt-install/lib/libbasalt.so: undefined symbol: vit_api_get_version
ERROR [t_slam_create] Failed to load VIT system library from 'libbasalt.so'
WARN [wmr_hmd_setup_trackers] Unable to setup the SLAM tracker
ERROR [wmr_create_headset] Failed to create WMR HMD device.
INFO [p_create_system] Creating system:
Builders:
qwerty: Qwerty devices builder
remote: Remote simulation devices builder
simulated: Simulated devices builder
rift_s: Oculus Rift S
rgb_tracking: RGB tracking based devices (PSVR, PSMV, ...)
steamvr: SteamVR proprietary wrapper (Vive, Index, Tundra trackers, etc.) devices builder
lighthouse: Lighthouse-tracked FLOSS (Vive, Index, Tundra trackers, etc.) devices builder
north_star: North Star headset
wmr: Windows Mixed Reality
xreal_air: Xreal Air
legacy: Legacy probing system
No builder selected in config (or wasn't compiled in)
Selected wmr because it was certain it could create a head
Using builder wmr: Windows Mixed Reality
Result: XRT_ERROR_DEVICE_CREATION_FAILED
ERROR [init_all] Could not create system!
INFO [print_linux_end_user_failed_information]
################################################################################
# #
# The Monado service has failed to start. #
# #
# If you want to report please upload the logs of the service as a text file. #
# You can also capture the output the monado-cli info command to provide more #
# information about your system, that will help diagnosing your problem. The #
# below commands is how you best capture the information from the commands. #
# #
# monado-cli info 2>&1 | tee info.txt #
# monado-service 2>&1 | tee logs.txt #
# #
################################################################################I did not have that issue with earlier versions.
Activity
undefined symbol: vit_api_get_versionThat is strange.
If you run
nm -gC --defined-only /path/to/libbasalt.sowhat do you get?I am currently getting the following, which includes
vit_api_get_version:0000000000000000 A BASALT_2.0.1 00000000000dd420 T vit_api_get_version 00000000000dd540 T vit_pose_destroy 00000000000dd560 T vit_pose_get_data 00000000000dd580 T vit_pose_get_features 00000000000dd570 T vit_pose_get_timing 00000000000dd510 T vit_tracker_add_camera_calibration 00000000000dd500 T vit_tracker_add_imu_calibration 00000000000522a0 T vit_tracker_create 00000000000dd440 T vit_tracker_destroy 00000000000dd490 T vit_tracker_enable_extension 00000000000dd480 T vit_tracker_get_enabled_extensions 00000000000dd470 T vit_tracker_get_supported_extensions 00000000000dd530 T vit_tracker_get_timing_titles 00000000000dd460 T vit_tracker_has_image_format 00000000000dd4d0 T vit_tracker_is_running 00000000000dd520 T vit_tracker_pop_pose 00000000000dd4f0 T vit_tracker_push_img_sample 00000000000dd4e0 T vit_tracker_push_imu_sample 00000000000dd4c0 T vit_tracker_reset 00000000000dd4a0 T vit_tracker_start 00000000000dd4b0 T vit_tracker_stopSame here:
$ nm -gC --defined-only /usr/lib/libbasalt.so.2.0.1 0000000000000000 A BASALT_2.0.1 00000000000a4390 T vit_api_get_version 00000000000a44b0 T vit_pose_destroy 00000000000a44d0 T vit_pose_get_data 00000000000a44f0 T vit_pose_get_features 00000000000a44e0 T vit_pose_get_timing 00000000000a4480 T vit_tracker_add_camera_calibration 00000000000a4470 T vit_tracker_add_imu_calibration 000000000003d6c0 T vit_tracker_create 00000000000a43b0 T vit_tracker_destroy 00000000000a4400 T vit_tracker_enable_extension 00000000000a43f0 T vit_tracker_get_enabled_extensions 00000000000a43e0 T vit_tracker_get_supported_extensions 00000000000a44a0 T vit_tracker_get_timing_titles 00000000000a43d0 T vit_tracker_has_image_format 00000000000a4440 T vit_tracker_is_running 00000000000a4490 T vit_tracker_pop_pose 00000000000a4460 T vit_tracker_push_img_sample 00000000000a4450 T vit_tracker_push_imu_sample 00000000000a4430 T vit_tracker_reset 00000000000a4410 T vit_tracker_start 00000000000a4420 T vit_tracker_stop $ ls -lah /usr/lib/libbasalt* lrwxrwxrwx 1 root root 14 Aug 15 17:02 /usr/lib/libbasalt.so -> libbasalt.so.2 lrwxrwxrwx 1 root root 18 Aug 15 17:02 /usr/lib/libbasalt.so.2 -> libbasalt.so.2.0.1 -rw-r--r-- 1 root root 6.1M Aug 15 16:58 /usr/lib/libbasalt.so.2.0.1In your previous log it seems dlopen was trying to open
/home/linus/dev-priv/vr/basalt-install/lib/libbasalt.sobut here you seem to have the .so in/usr/lib/libbasalt.so.Try specifying the .so location explicitly by setting the environment variable
export VIT_SYSTEM_LIBRARY_PATH=/usr/lib/libbasalt.sobefore executing monado.Other than that I am unfortunately without the time to properly try a debian sid installation to debug this and the latest monado/basalt main branches seem to work on my systems.
Urgh, that was indeed it! Doing a "mv ~/vr/basalt-install ~/vr/basalt-install-old" fixed it... I guess that originally came from some old steps/instructions with some bsltinstall environment variable.
But I still don't quite get why it tried to use that now. None of these find that directory:
"grep "basalt-install" ~/.local/bin/monado-service", "grep -r "basalt-install" ~/dev-priv/vr/basalt", "grep -r "basalt-install" ~/dev-priv/vr/monado". Only this finds it? -> "grep -r "basalt-install" ~/dev-priv/vr/basalt-deps" (but I haven't touched/used that directory since more than a year now?). I also don't have any basalt environment variable in my ~/.zshrc for quite a while now ("env | grep bslt" and "env | grep basalt" both empty)
.oO some cmake remembrance issues somewhere? Where one would need to do a clean & rebuild twice?
You may have that directory in your
PKG_CONFIG_PATH/LD_LIBRARY_PATH/LIBRARY_PATHas was the old readme instructed? You can doecho PKG_CONFIG_PATH, etc to check.The new readme urges you to install without specifying installation directory so it goes to
/usr/libby default, which is usually one of the default directories to look for libraries for pkgconfig/ld/gcc/cmake/etc on most linux systems.Regarding cmake you can try deleting the build directories of both basalt and monado and that should be it to clean any cmake cache.
