-
Notifications
You must be signed in to change notification settings - Fork 60
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
forcing internal link mode on macOS causes "unexpected reloc for dynamic symbol" link errors #84
Comments
v0.0.0-20210410170116-ea3d685f79fb is a pretty old version of glfw/v3.3. Can you try the latest and see if that fixes it? go get github.com/go-gl/glfw/v3.3/glfw
go run . If so, we should update the dependency versions in the go.mod. |
Same issue with head of master. The project I originally noticed this on doesn't seem to work with any versions v3.2/v3.3. I'm not sure if an OS update has caused some headers to become mis-aligned. Is there any other system information I can gather to help get more of a handle on where the issue is? |
Thanks for trying. That's unexpected. I have a similar setup but I can't reproduce the problem so far. A few more ideas to try:
|
|
That's quite odd. I'm finding similar errors in issues like mattn/go-sqlite3#112, mattn/go-sqlite3#404. They suggest this might be caused by something being wrong with the Xcode installation. Can you also post |
|
Ah! |
That looks relevant! Please try without forcing internal link mode (which isn't supported with cgo, see golang/go#38918). The go command should default to external automatically (see mattn/go-sqlite3#404 (comment)). |
Thanks so much for your help (and sorry but glad that it was user error)! I had added the linkmode flag to my dotfiles on a different computer and didn't even remember the change. |
I tried to compile an existing project that uses
go-gl/glfw/v3.2
and saw link-time errors on MacOS which did not occur previously on the same version.Running the gl21-cube example has the same link error.
Any advise on how to help diagnose this?
The text was updated successfully, but these errors were encountered: