Fix Linux build error for DuckDB 0.6.1

[begelundmuller]

Upgrading to DuckDB 0.6.1 in #1438 caused Linux builds to fail, so we reverted to DuckDB 0.6.0 in #1442.

Here are the build errors we got: https://github.com/rilldata/rill-developer/actions/runs/3691803710/jobs/6250128616

Some observations:

• These look like linker errors to me – maybe we're linking to a wrong version of the c++ standard library on Linux?
• This is probably a problem in the setup in go-duckdb, not in rill-developer
• The linking is configured in go-duckdb here: https://github.com/marcboeker/go-duckdb/blob/master/cgo_static.go
  • The notable line is: #cgo linux,amd64 LDFLAGS: -lstdc++ -lm -ldl -L${SRCDIR}/deps/linux_amd64
• You can also look at duckdb/duckdb@v0.6.0...v0.6.1 to see what might have changed in DuckDB from v0.6.0 (which compiles) to v0.6.1 (which doesn’t compile on Linux)

[begelundmuller]

Some more observations here:

• The static library builds of DuckDB are built using ubuntu-latest on Linux. Between v0.6.0 and v0.6.1, that runner was upgraded from Ubuntu 20.04.5 to Ubuntu 22.04.01
• Similar bugs have been reported in go-duckdb repo here:
  • Question: Provided duckdb binary references shared libraries (libstdc++.so.6, libm.so.6 etc) marcboeker/go-duckdb#54
  • Compilation failure on Linux marcboeker/go-duckdb#58

Maybe the problem is that libc++ is not getting statically linked into the static libraries built in go-duckdb. Maybe this could be solved by making the static library built here fully static?

[rakeshsharma14317]

More findings while making build fully static linking

Tried with all the possible ways of fully static linking, Looks like some issues with latest ubuntu GHC.
Option which recommended is to downgraded to 20.04 version.
Ref:

• CI fails linking package resolve with ubuntu-latest (which is 22.04) but works fine with 20.04 haskell/cabal#8630
• deploy action broken by switch from ubuntu-20.04 to ubuntu-22.04 agda/agda#6384

[mindspank]

Stale