Help compiling duckdb and error loading postgres: `undefined symbol: _ZTIN6duckdb7CatalogE`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cmake, cpp, postgresql
- Domain
- build-system, databases
Research direction
Start with the duckdb-postgres build instructions and the extension_config.cmake entry for postgres_scanner, then reproduce the issue using GEN=ninja EXTENSION_CONFIGS="extension_config.cmake" make. Compare the v1.3.2 DuckDB checkout and the referenced duckdb-postgres revision to determine what configuration or revision is required. Done means loading postgres_scanner without the undefined Catalog symbol.
Written by the indexing model from the issue text.
Description
Apologies if this is not the right place to ask for help.
When LOADing the postgres extension that I compiled myself, I am running into
Extension "/home/mzabani/duckdb/build/release/extension/postgres_scanner/postgres_scanner.duckdb_extension" could not be loaded: /home/mzabani/duckdb/build/release/extension/postgres_scanner/postgres_scanner.duckdb_extension: undefined symbol: _ZTIN6duckdb7CatalogE
I have duckdb cloned and checked out at the v1.3.2 tag, and duckdb-postgres cloned and checked out at c3024b5c8570695dc73422066fcd221ed64761de, which seemed like the best match since the duckdb git submodule is also at v1.3.2.
I then have the following extension_config.cmake file in the duckdb repo (last line might be the actual relevant one):
duckdb_extension_load(autocomplete)
duckdb_extension_load(core_functions)
duckdb_extension_load(httpfs SOURCE_DIR /home/mzabani/duck-read-cache-fs/duckdb-httpfs INCLUDE_DIR /home/mzabani/duck-read-cache-fs/duckdb-httpfs/extension/httpfs/include)
duckdb_extension_load(cache_httpfs SOURCE_DIR /home/mzabani/duck-read-cache-fs)
duckdb_extension_load(ducklake SOURCE_DIR /home/mzabani/ducklake)
duckdb_extension_load(icu)
duckdb_extension_load(json)
duckdb_extension_load(parquet)
duckdb_extension_load(postgres_scanner DONT_LINK SOURCE_DIR /home/mzabani/duckdb-postgres)
After that I ran GEN=ninja EXTENSION_CONFIGS="extension_config.cmake" make to compile.
Is this something obvious I'm missing from the build instructions?
Thanks in advance.
- Dominant language
- C++
- Stars
- 372
- Forks
- 107
- Avg merge
- 13h 55m
- Merged PRs (30d)
- 13
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from duckdb/duckdb-postgres
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
duckdb/duckdb-postgres#575 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
duckdb/duckdb-postgres#564 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
duckdb/duckdb-postgres#491 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
duckdb/duckdb-postgres#487 · 1 comment ·
Maintainers usually reply within 1 day
-
After `COPY DATABASE FROM <pg>`, the types from pg are improperly formatted in `EXPORT` commandsOpen
Difficulty 4/5 3-5 days Newbie friendliness 48/100
duckdb/duckdb-postgres#429 ·
Maintainers usually reply within 1 day
All issues in duckdb/duckdb-postgres
Similar issues
-
agent:Windows bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
? - Needs Triage bot_watch bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
NVIDIA/cudf-spark-jni#5267 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
(S1 - Need confirmation)
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
CleverRaven/Cataclysm-DDA#88974 ·
Maintainers usually reply within 1 day