What happens?

For Go library, we have been using libduckdb_bundle.a until v1.2.1
https://github.com/marcboeker/go-duckdb#linking-a-static-library
With a following commit, our life gets a bit bitter
2ae23d6

To Reproduce

We used to build our DuckDB embedding program this way:

export DUCKDB_VERSION='v1.2.1'

wget https://github.com/duckdb/duckdb/releases/download/${DUCKDB_VERSION}/static-lib-linux-amd64.zip \
    && unzip -o static-lib-linux-amd64.zip

CGO_LDFLAGS="-lstdc++ -lm -lc++ -lduckdb_bundle -L$(pwd)" \
    go build \
    --ldflags '-extldflags "-static"' \
    -tags="duckdb_use_static_lib" \
    ./cmd/...

OS:

amd64

DuckDB Version:

1.2.2

DuckDB Client:

Go

Hardware:

No response

Full Name:

Tomáš Karela Procházka

Affiliation:

Dataddo

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have not tested with any build

Did you include all relevant data sets for reproducing the issue?

No - Other reason (please specify in the issue body)

Did you include all code required to reproduce the issue?

• Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?

• Yes, I have