Skip to content

ros2-spatio-temporal-voxel-layer 2.7.0 is built against OpenVDB 13.1 but allows installation with OpenVDB 13.2 #186

Open

Description

@mwiesnero2c

Solution to issue cannot be found in the documentation.

  • I checked the documentation.

ROS distribution

rolling

Issue

Description

It appears that the RoboStack package ros2-spatio-temporal-voxel-layer 2.7.0 was built against OpenVDB 13.1, while its package metadata allows installation with OpenVDB 13.2. This results in an ABI mismatch.

Steps to reproduce

  1. Create environment with the following pixi.toml:
[workspace]
name = "stvl-openvdb-reproducer"
channels = ["robostack-lyrical", "conda-forge"]
platforms = ["linux-64"]
 
[dependencies]
ros2-spatio-temporal-voxel-layer = "*"
  1. Check which OpenVDB version the STVL library was linked against: readelf -d .pixi/envs/default/lib/libspatio_temporal_voxel_layer_core.so | grep NEEDED. Observe libopenvdb.so.13.1
  2. Check the installed OpenVDB package: pixi list | grep openvdb. Observe openvdb 13.2.0
  3. Check runtime library resolution: ldd .pixi/envs/default/lib/libspatio_temporal_voxel_layer_core.so | grep openvdb . Observe libopenvdb.so.13.1 => not found

Additional information

The package metadata declares openvdb >=13.1.0,<14.0a0 (see output of pixi search ros2-spatio-temporal-voxel-layer).
However, the binary appears to require OpenVDB 13.1 specifically.

Creating a symlink from libopenvdb.so.13.1 to libopenvdb.so.13.2 removes the loader error but results in undefined symbol:*_ZN7openvdb*v13_110initializeEv which suggests an ABI incompatibility between OpenVDB 13.1 and 13.2.

Workaround

Pinning OpenVDB to 13.1.x resolves the issue:

[dependencies]
openvdb = "13.1.*"

pixi list output

pixi_list.txt

Installed packages

The full pixi list output exceeds GitHub's issue size limit. It's attached as a file (see above).

Environment info

System
------------
       Pixi version: 0.83.0
        TLS backend: rustls
           Platform: linux-64
   Virtual packages: __unix=0=0
                   : __linux=6.17.0=0
                   : __glibc=2.39=0
                   : __amdgpu=0=0
                   : __amdgpu_arch=11.5.2=0
                   : __archspec=1=zen5
          Cache dir: /home/marekwiesner/.cache/rattler/cache
       Auth storage: /home/marekwiesner/.rattler/credentials.json
   Config locations: No config files found

Global
------------
            Bin dir: /home/marekwiesner/.pixi/bin
    Environment dir: /home/marekwiesner/.pixi/envs
       Manifest dir: /home/marekwiesner/.pixi/manifests/pixi-global.toml

Workspace
------------
               Name: stvl-openvdb-reproducer
      Manifest file: /home/marekwiesner/code/stvl-openvdb-reproducer/pixi.toml
       Last updated: 02-11-2026 11:06:00

Environments
------------
        Environment: default
           Features: default
           Channels: robostack-lyrical, conda-forge
   Dependency count: 1
       Dependencies: ros2-spatio-temporal-voxel-layer
   Target platforms: linux-64
  Resolved platform: linux-64 (archspec=x86_64, glibc=2.28, linux=4.18, __unix)
   Minimum platform: linux-64 (__glibc >=2.17,<3.0.a0, __glibc >=2.28,<3.0.a0, __unix)
    Prefix location: /home/marekwiesner/code/stvl-openvdb-reproducer/.pixi/envs/default

Activity

  1. Tobias-Fischer commented on Nov 2, 2026

    @Tobias-Fischer
    Collaborator

    Looks like an issue on OpenVDB feedstock. We need to change the run exports to pin minor version there and open a conda-forge admin request to patch the repodata of existing packages. Are you ok to give this a go?

  2. mwiesnero2c commented on Nov 2, 2026

    @mwiesnero2c
    Author

    Yes, I will have a look at the OpenVDB feedstock and prepare a PR if that is the expected fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions