Skip to content

libduckdb.so name is different for compilation and runtime #64

@AmebaBrain

Description

@AmebaBrain

With a new 1.1.3 release it's required to rename libduckdb.so library to libduckdb.1.1.3.so to have compilation succeeded.

# Rename library file with version number
mv "libduckdb.${LIB_EXT}" "libduckdb.${DUCKDB_VERSION}.${LIB_EXT}"

But in the same time, during runtime the compiled duckdb_fdw.so still expects the duckdb library to be named as libduckdb.so and not libduckdb.1.1.3.so. Otherwise, it fails with

psql:/docker-entrypoint-initdb.d/fdw_setup.sql:1: ERROR:  could not load library "/usr/lib/postgresql/17/lib/duckdb_fdw.so": libduckdb.so: cannot open shared object file: No such file or directory

Is it expected behavior? Use libduckdb.1.1.3.so for the compilation but libduckdb.so during runtime?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions