-
-
Notifications
You must be signed in to change notification settings - Fork 227
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
exec: "FR": executable not found in %PATH% #317
Comments
Hmm strange. Does it also do that when compiling a simple cgo program? Perhaps you can try
|
@s-nieuwlandt-dev echo %CC%
echo %GCC% This is how compiler used by cgo is set. It basically takes one from // gccBaseCmd returns the start of the compiler command line.
// It uses $CC if set, or else $GCC, or else the compiler recorded
// during the initial build as defaultCC.
// defaultCC is defined in zdefaultcc.go, written by cmd/dist.
func (p *Package) gccBaseCmd() []string {
// Use $CC if set, since that's what the build uses.
if ret := strings.Fields(os.Getenv("CC")); len(ret) > 0 {
return ret
}
// Try $GCC if set, since that's what we used to use.
if ret := strings.Fields(os.Getenv("GCC")); len(ret) > 0 {
return ret
}
return strings.Fields(defaultCC(goos, goarch))
}
func defaultCC(goos, goarch string) string {
switch goos+`/`+goarch {
}
return "gcc"
} So you either have environment variable set for |
Hi ! Thanks for your answers :) I can reproduce the error on the snippet, and effectively, my So clearly this is not a go-sdl2 issue :) Thanks for the informations and your time ! |
Hi !
Thanks for your library, it's really a good job :)
I faced an issue when doing a
go get -v github.com/veandco/go-sdl2/sdl
:My configuration is :
The MinGW bin directories are added to my PATH.
When I run a
go build -v -work -x -n
, I can see that the library use cgo, which in turn call the C compilation command, by usingFR
instead ofgcc
.As a workaround, I create a copy of my
gcc.exe
file in theMinGW\bin
directory, and rename itFR.exe
(ugly, but do the job).I'm still analysing why the cgo executable will change the executable's name, but if you have an info about this, I'm interested :)
The text was updated successfully, but these errors were encountered: