Building mach on Mac OS fails with hash mismatch #1081
Labels
No labels
CI
all
basisu
blog
bug
build
contributor-friendly
core
correctness
deferred
dev
direct3d-headers
docs
driver-os-issue
duplicate
dxcompiler
editor
examples
experiment
feature-idea
feedback
flac
freetype
gamemode
gkurve
glfw
gpu
gpu-dawn
harfbuzz
help welcome
in-progress
infrastructure
invalid
libmach
linux-audio-headers
long-term
mach
mach.gfx
mach.math
mach.physics
mach.testing
model3d
needs-triage
object
opengl-headers
opus
os/linux
os/macos
os/wasm
os/windows
package-manager
priority
proposal
proposal-accepted
question
roadmap
slipped
stability
sysaudio
sysgpu
sysjs
validating-fix
vulkan-zig-generated
wayland-headers
website
wontfix
wrench
www
x11-headers
xcode-frameworks
zig-update
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
hexops/mach#1081
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Steps to reproduce
zig buildResult
Additional information
mach_corehas the same issue, but when fetchingmach_duskzigwas installed viabrewHello!
The main repository has an issue currently, but mach-core is promised to work.
Please make sure you are using a supported Zig version: https://machengine.org/about/zig-version/
The one provided by brew may not be sufficient, hash mismatch is one sign of this.
If you are using a Linux machine with btrfs filesystem (e.g. Fedora), you may need to set
ZIG_BTRFS_WORKAROUND=1to workaround a bug in Zig / the Linux kernel.Let me know if that helps.
Hi! I also had problems building the latest stuff.
The expected zig version (as indicated by the .zig-version file and recent commits) is 0.12.0-dev.1092+68ed78775. But your download link currently points at an earlier version. Shouldn't that be updated in in sync with .zig-version?
@kamidev yep, I've updated the website. In the future
.zigversionand the website will always be in sync.If anyone encounters more issues here, feel free to open a new issue.