Using the extension fails with "undefined symbol: _ZTIN6duckdb7CatalogE"

[ciupicri]

What happens?

I've build DuckDB along with the sqlite extension, but I can't use it. Maybe the issue is with the core or the way I compile it, not this extension itself.

Running .../build/release/duckdb -unsigned -readonly g.sqlite gives me:

Error: unable to open database "g.sqlite": IO Error: Extension "/home/ciupicri/.duckdb/extensions/043a0d75d6/linux_amd64/sqlite_scanner.duckdb_extension" could not be loaded: /home/ciupicri/.duckdb/extensions/043a0d75d6/linux_amd64/sqlite_scanner.duckdb_extension: undefined symbol: _ZTIN6duckdb7CatalogE

or

Error: unable to open database "g.sqlite": IO Error: Extension "/home/ciupicri/.duckdb/extensions/v1.1.3/linux_amd64/sqlite_scanner.duckdb_extension" could not be loaded: /home/ciupicri/.duckdb/extensions/v1.1.3/linux_amd64/sqlite_scanner.duckdb_extension: undefined symbol: _ZTIN6duckdb7CatalogE

depending on the version used.

To Reproduce

1. Clone the duckdb repository
2. Clone the sqlite_scanner repository
3. Build DuckDB and the sqlite extension at the same time:

cd duckdb
cat > extension/extension_config_local.cmake << EOF
duckdb_extension_load(sqlite_scanner
	DONT_LINK
	SOURCE_DIR $(realpath ../sqlite_scanner)
)
EOF

GEN=ninja DUCKDB_EXTENSIONS='autocomplete;icu;fts;httpfs;json' BUILD_PYTHON=1 BUILD_JEMALLOC=1 make

4. Install the extensions:

for i in build/release/extension/*/*.duckdb_extension; do ./build/release/duckdb -c "INSTALL '"${i}"';"; done

OS:

Fedora Linux 41 x64
cmake-3.30.5-1.fc41.x86_64
ninja-build-1.12.1-3.fc41.x86_64
gcc-14.2.1-3.fc41.x86_64

SQLite Version:

3.46.1-1.fc41.x86_64

DuckDB Version:

v1.1.3 or v1.1.4-dev1845 043a0d75d6

DuckDB Client:

CLI

Full Name:

Cristian Ciupitu

Affiliation:

none

Have you tried this on the latest main branch?

• I agree

Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?

• I agree

[Mytherin]

This seems like an issue with the way you are compiling the extension - I would recommend sticking to the README here. Help with custom compilation setups is out of scope here.