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

Bug: Unexpected behaviour when building extension before building kuzu from source #4652

Open
prrao87 opened this issue Dec 18, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@prrao87
Copy link
Member

prrao87 commented Dec 18, 2024

Kùzu version

master

What operating system are you using?

macOS Sonoma 14.5

What happened?

When building from source, running the build steps in the following order doesn't create a build directory in tools/shell and tools/python_api, which is unexpected behaviour.

This doesn't work

make extension-release NUM_THREADS=20
make release NUM_THREADS=20
make python NUM_THREADS=20

When run in this order, the extension release directory has a build directory in it, but there is no build directory in the tools/shell and tools/python_api directories as we might expect.

This works

make release NUM_THREADS=20
make python NUM_THREADS=20
make extension-release NUM_THREADS=20

When run in this order, all the required directories have a build directory and I can run the Kùzu CLI, Python client and extensions in both with no issues.

I think there's a flag missing somewhere that causes the build to not work when run as per the order shown in the former case?

Are there known steps to reproduce?

No response

@prrao87 prrao87 added the bug Something isn't working label Dec 18, 2024
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