-
Notifications
You must be signed in to change notification settings - Fork 15
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
Build error on macOS #153
Comments
Thanks for reporting. Unfortunately I do not have a MacOS test environment. But thanks to your clear error description I see two issues:
I am working on supporting MacOS based on your information in #157. |
NOTE: I just realized that CI in #157 fails. Obviously it only makes sense to test this on MacOS after CI passes. |
I was able to build successfully on MacOS with #157 . Both issues are resolved when I run build with the command ./build.sh.
|
I looked at the CI build failures and tried to replicate them. I ran these commands to run tests Got similar test failures as the CI tests.
Attached test log files. |
Thanks for helping out here. The failing tests are all related to testing gWhisper against a test server specifically started for the test. It is kind of hard for me to debug, as I only have the CI to test on, so I am quite happy that you could replicate on your local setup. Could you maybe try starting the test server manually and run gwhisper with some arbitrary RPCs against it on your setup? |
Describe the bug
Running the build with the default configuration using build.sh fails with the error
To Reproduce
Run build.sh
Expected behavior
Build completes without eerror
Provide details about your environment
gwhisper --version
output: Unable to buildAdditional context
Full log attached. Retried the build with the test server turned off using the command
cmake .. -D GWHISPER_BUILD_TESTSERVER=OFF
This time got another linker error
Work around:
Commented out
stdc++fs
in src/libLocalDescriptorCache/CMakeLists.txt and src/utils/CMakeLists.txt to be able to build gwhisper binary.build.log
The text was updated successfully, but these errors were encountered: