Skip to content

Don't emit STB_UNIQUE symbols in GCC for vortex-duckdb #8913

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
myrrc merged 1 commit into from
Jul 23, 2026
Merged

Don't emit STB_UNIQUE symbols in GCC for vortex-duckdb #8913

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions vortex-duckdb/build.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -519,6 +519,12 @@ fn compile_cpp(duckdb_include_dir: &Path) {
.std("c++20")
.flags(["-Wall", "-Wextra", "-Wpedantic", "-Werror"])
.cpp(true)
// Duckdb 1.5.5 uses C++11. spatial_overrides.o uses
// duckdb::ScalarFunctionCatalogEntry::Name which is constexpr but not
// inline. Our code uses C++20 where constexpr implies inline. GCC
// emits this symbol with STB_GNU_UNIQUE and this conflicts on link stage
// in duckdb-vortex where libvortex_duckdb.a is linked statically
.flag_if_supported("-fno-gnu-unique")
// We don't want compiler warnings inside duckdb headers, pass as flags
.flag("-isystem")
.flag(duckdb_include_dir)
Expand Down
Loading