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

Clean build of v1.5.12 fails due to v8 #793

Open
KVeschgini opened this issue Jul 4, 2024 · 5 comments
Open

Clean build of v1.5.12 fails due to v8 #793

KVeschgini opened this issue Jul 4, 2024 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@KVeschgini
Copy link

What's wrong
A clean build on M2 Mac using Docker fails due to v8.

How to reproduce

git clone --recurse-submodules [email protected]:timeplus-io/proton.git

cd proton

./docker/packager/packager --package-type binary --docker-image-version clang-16 --proton-build --enable-proton-local --output-dir `pwd`/build_output --compiler clang-16-darwin

Error message
Build fails with

ninja: error: 'contrib/v8-cmake/bytecode_builtins_list_generator', needed by 'contrib/v8-cmake/generated/builtins-generated/bytecodes-builtins-list.h', missing and no known rule to make it
@KVeschgini KVeschgini added the bug Something isn't working label Jul 4, 2024
@yokofly yokofly self-assigned this Jul 4, 2024
@yokofly
Copy link
Collaborator

yokofly commented Jul 4, 2024

edit: add brew install
I probably know something.. sorry about this.
the --compiler clang-16-darwin will jump to cross compile,
we hard code some build binary for the v8.

would you like to use directly bare metal build instead of docker?
https://github.com/timeplus-io/proton/blob/develop/BUILD.md#bare-metal-build-5

the proton server final is a static library. the fresh build basically need about 90 minutes.
also you can download the binary or pull the docker or brew install directly to take a try proton.

@KVeschgini
Copy link
Author

Thanks, I am aware that the binary exists and I am already using it. I am trying to build proton to be able to work on the source code. The build also fails under wsl and on a ubuntu machine. I will try again, document the process and then make a bug ticket.

@yokofly
Copy link
Collaborator

yokofly commented Jul 4, 2024

really appreciate your trial. I check the code again, the "docker build for macOS" issue may not have a quick fix.
Would you mind trying the bare-metal build instead? the macOS use the dockered low level is based on arm/x86 linux.

Regarding the WSL / Ubuntu build failure, this seems to be an issue.
Some of our colleagues already use WSL for their daily development and debugging.

@KVeschgini
Copy link
Author

Bare-metal build worked for me after upgrading xcode to version 15.4.

@yokofly
Copy link
Collaborator

yokofly commented Jul 5, 2024

glad to hear that. There's a current issue with macOS where the stacktrace only works in debug mode, but there's no stacktrace when you throw an exception directly (ClickHouse already has a patch to fix this, but I don't have the time to back port it).

Apart from this problem, macOS also doesn't have jemalloc && sanitizer. thoes are some potential issues we currently encountered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants