Diverging DUCKDB_PLATFORM for DuckDB and Rusty_Quack Extension

[hknlof]

Hi Team,

TL;DR:
I would have expected the CLI and Extension to build with linux_amd64_gcc4 for DUCKDB_PLATFROM.
CLI builds to linux_amd64 and rust extension to linux_amd64_gcc4.

I am not sure, if I have build duckdb and the template extension as intended.
I run into the following issue:

❯ ./build/release/duckdb
v1.2.1-dev63 a35a3fba95
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
D install rusty_quack from '../extension-template-rs/build/release/extension';
IO Error:
Failed to install 'rusty_quack'
The file was built for the platform 'linux_amd64_gcc4', but we can only load extensions built for platform 'linux_amd64'.
D pragma platform;
┌─────────────┐
│  platform   │
│   varchar   │
├─────────────┤
│ linux_amd64 │
└─────────────┘
D

This makes sense. As the DUCKDB_PLATFORM is detected as linux_amd64_gcc4 via pip install in venv from the Makefile in this extension.
According to Platforms, I would have expected, the CLI to have been build to the same platform. Instead it is build to linux_amd64 as you can see above.

Both duckdb and the extension were build with make and make configure && make release accordingly.

OS and GCC:

~/duckdb
❯ uname -a
Linux dev 6.12.8 #1-NixOS SMP PREEMPT_DYNAMIC Thu Jan  2 09:34:26 UTC 2025 x86_64 GNU/Linux

~/duckdb
❯ gcc --version
gcc (GCC) 14.2.1 20241116
Copyright (C) 2024 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

EDIT: Corrected build command