-
Notifications
You must be signed in to change notification settings - Fork 118
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
fix(watchman) #7226
fix(watchman) #7226
Conversation
Judging from the logs, we may need to update folly to a more recent version. The correct version (2024.09.09.00) has not yet been released on pkgx. |
yeah, they update every week, but have to be built in a specific order. i'll get them finished tomorrow. though watchman hasn't built for our linux targets in a few months. |
Gotcha. Thanks so much for maintaining these. By the way, what's the best
way to set the build-time WATCHMAN_STATE_DIR so it points to the .pkgx
directory?
…On Thu, 12 Sept 2024, 07:11 Jacob Heider, ***@***.***> wrote:
yeah, they update every week, but have to be built in a specific order.
i'll get them finished tomorrow. though watchman hasn't built for our linux
targets in a few months.
—
Reply to this email directly, view it on GitHub
<#7226 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABREPV4F2DVPF5ZNAV77UG3ZWDE35AVCNFSM6AAAAABN7UUBPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBUHA4DQMBUG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
that should probably be an |
@@ -46,7 +46,7 @@ build: | |||
WATCHMAN_STATE_DIR: "{{prefix}}/var/run/watchman" | |||
CMAKE_ARGS: | |||
- -DCMAKE_INSTALL_PREFIX="{{prefix}} | |||
- -DCMAKE_PREFIX_PATH=$(echo $LIBRARY_PATH | sed 's/\/lib:/:/g; s/\/lib$//') | |||
- -DCMAKE_PREFIX_PATH=$(echo $LIBRARY_PATH | sed 's/\/lib:/;/g; s/\/lib$//') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CMAKE_PREFIX_PATH should be fixed in pkgx 1.2.1 again. sorry for the breakage!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah okay haha I was wondering what was happening...
428c792
to
aff68d7
Compare
No description provided.