-
Notifications
You must be signed in to change notification settings - Fork 243
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
cc: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory #110
Comments
Maybe your w64devkit zip didn't unpack fully or correctly. Or perhaps
you've got one or more environment variables interfering with GCC. Or
you're picking up the wrong GCC, though the version number is correct.
Check that cc1.exe is present. You can find it deep under libexec, and
22.8M in size. A test that eliminates the environment as a factor:
$ env - PATH="$W64DEVKIT_HOME/bin" cc -S -xc -o - - <nul
That exercises just cc1 and should print three assembly directives without
errors. If that works then check your environment variables for anything
funny.
|
I've had the same issue. Windows Defender identified w64devkit as malware and probably messed with some things there as a result, even when allowing it. I disabled Windows Defender and unzipped the release using 7zip instead of Windows Explorer, then it worked fine. |
unzipped the release using 7zip
Thanks for that detail. It's significant, and I should suggest it myself
in the future. Browser-downloaded files get a "Mark of the Web" in their
metadata. Windows' built-in unzip program propagates it to files extracted
from a marked archive, and files with the mark are treated with extreme
prejudice. However, 7zip does not do this by default (and didn't support
it at all until very recently). In general, unpacking zip files with a
third-party tool — including busybox-w32 unzip — reliably clear the MotW.
This is an additional reason for me to consider distributing w64devkit as
a self-extracting archive (#87). Besides avoiding the bugs (#58) and poor
performance of Windows' built-in zip tool, it would resolve MotW issues,
reducing the problem to a single "suspicious" binary, the self-extractor
itself, which would be feasible to mitigate with SignTool or osslsigncode.
Well-built self-extractors are still valid archives, and wouldn't require
running the self-extractor itself just to access the contents.
https://en.wikipedia.org/wiki/Mark_of_the_Web
|
Closed
This particular issue should be mitigated with the new 7z SFX distribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Attempting to build with 'make' fails with:
I've attempted to resolve this by disabling Windows Defender.
The text was updated successfully, but these errors were encountered: