gpu: Missing cc on up-to-date Linux install #281
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#281
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?
I just tried to go through the install from source as described in the README.
It mentions that besides Git and Zig, no build dependencies are needed.
I am not sure this is true, as evidenced below:
The following was the result. With the error at the bottom:
ccdoes not exist on my system.This system being: Linux boops 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
I deliberately did not install things like GCC on this system, as I wanted to do as much as possible using Zig.
can you run
zig build -Ddawn-from-source=trueagain with--verboseargument passed?This yields:
Which, I guess doesn't add anything new. Unless I am missing something.
This is a Zig specific issue which I have faced before in other projects. It basically happens when trying to compile a C project in a system missing a C compiler. I dont know of any solution or as to what extend this is a real issue.
Maybe try passing the exact gnu/musl version in the triplet:
zig build -Dtarget=x86_64-linux-gnu-2.34??If you don't pass a cross-compilation target (
-Dtarget=x86_64-linux), Zig will attempt to use your host toolchain in some cases (compiler, libc version, etc.)Passing a cross-compilation target should fix the issue as @iddev5 mentioned. Let us know if not!
This seems to have done the trick. Thanks.