Skip to content
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.

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

Debug build report error if DUCKDB_PLATFORM is not explicitly set while release build report does NOT need to provide DUCKDB_PLATFORM #76

Open
qubin-ben opened this issue Aug 13, 2024 · 0 comments

Comments

@qubin-ben
Copy link

Below is the error message of my screen. The error goes aways if I explicitly set DUCKDB_PLATFORM=linux_amd64. While I do NOT encounter this error in release build and I believe it is better to auto set DUCKDB_PLATFORM in make script.

============== error message on my screen =====================

make debug
mkdir -p build/debug &&
cmake -DEXTENSION_STATIC_BUILD=1 -DDUCKDB_EXTENSION_CONFIGS='/data2/aaa/git/duckdb_mysql/extension_config.cmake' -DOSX_BUILD_ARCH= -DDUCKDB_EXPLICIT_PLATFORM='' -DCMAKE_BUILD_TYPE=Debug -S "./duckdb/" -B build/debug &&
cmake --build build/debug --config Debug
-- Running vcpkg install
warning: Embedding vcpkg-configuration in a manifest file is an EXPERIMENTAL feature.
Detecting compiler hash for triplet x64-linux...
Compiler found: /opt/rh/gcc-toolset-11/root/usr/bin/c++
All requested packages are currently installed.
Total install time: 339 ns
The package libmysql provides CMake targets:

find_package(libmysql REQUIRED)
target_link_libraries(main PRIVATE ${MYSQL_LIBRARIES})

-- Running vcpkg install - done
-- git hash 1f98600c2c, version v1.0.0, extension folder v1.0.0
-- Extensions will be deployed to: /data/home/aaa/git/duckdb_mysql/build/debug/repository
-- Load extension 'mysql_scanner' from '/data/home/aaa/git/duckdb_mysql' @ 29c1f12
-- Load extension 'parquet' from '/data/home/aaa/git/duckdb_mysql/duckdb/extensions' @ 1f98600c2c
-- Load extension 'jemalloc' from '/data/home/aaa/git/duckdb_mysql/duckdb/extensions' @ 1f98600c2c
-- Extensions linked into DuckDB: [parquet, jemalloc]
-- Extensions built but not linked: [mysql_scanner]
-- Tests loaded for extensions: [mysql_scanner]
-- Configuring done (4.4s)
-- Generating done (0.4s)
-- Build files have been written to: /data/home/aaa/git/duckdb_mysql/build/debug
gmake[1]: Entering directory '/data2/aaa/git/duckdb_mysql/build/debug'
gmake[2]: Entering directory '/data2/aaa/git/duckdb_mysql/build/debug'
gmake[3]: Entering directory '/data2/aaa/git/duckdb_mysql/build/debug'
gmake[3]: Leaving directory '/data2/aaa/git/duckdb_mysql/build/debug'
[ 0%] Built target duckdb_yyjson
gmake[3]: Entering directory '/data2/aaa/git/duckdb_mysql/build/debug'
gmake[3]: Leaving directory '/data2/aaa/git/duckdb_mysql/build/debug'
[ 1%] Built target duckdb_platform_binary
gmake[3]: Entering directory '/data2/aaa/git/duckdb_mysql/build/debug'
gmake[3]: Leaving directory '/data2/aaa/git/duckdb_mysql/build/debug'
gmake[3]: Entering directory '/data2/aaa/git/duckdb_mysql/build/debug'
==1847247==ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD.
Provide explicit DUCKDB_PLATFORM=your_target_arch to avoid build-type detection of the platform
gmake[3]: *** [CMakeFiles/duckdb_platform.dir/build.make:70: CMakeFiles/duckdb_platform] Error 1
gmake[3]: Leaving directory '/data2/aaa/git/duckdb_mysql/build/debug'
gmake[2]: *** [CMakeFiles/Makefile2:3699: CMakeFiles/duckdb_platform.dir/all] Error 2
gmake[2]: Leaving directory '/data2/aaa/git/duckdb_mysql/build/debug'
gmake[1]: *** [Makefile:136: all] Error 2
gmake[1]: Leaving directory '/data2/aaa/git/duckdb_mysql/build/debug'
make: *** [extension-ci-tools/makefiles/duckdb_extension.Makefile:53: debug] Error 2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant