-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
cmd/link: external linking fails with -s on darwin #10254
Comments
|
Even our misc/ccgo/test fails:
Alex |
The problem is that when -s is set, cmd/internal/ld will not generate the
COFF
symbol table, however, the symbol table is essential for external linking.
For now, please don't pass -ldflags -s if you're external linking, instead,
use
-ldflags "-extldflags -s".
|
It is Go linker crashing. It is bug that needs to be fixed. I don't have computer to confirm, but I suspect it is crashing because we ncoffsym++ in initdynimport. Why do we ncoffsym++ if we don't store symbols into coffsym. ncoffsym will get reset to 0 later on anyway in addpesymtable. I think our logic is flawed. Alex |
Summary: On OS X, asciidoc fails to find the executable of the Python interpreter, leading it to try and execute the empty string. We can fix this by overriding the autodetected interpreter with an attribute. The environment Bazel runs builds in does not include the path for graphviz on OS X. This CL adds logic to configure this in setup_bazel.sh. Finally, there's a Go issue on OS X that we're hitting. (golang/go#10254). Stop hitting it. Reviewers: shahms, fromberger, schroederc Reviewed By: schroederc Differential Revision: https://phabricator-dot-kythe-repo.appspot.com/D319
It sounds like if -s is given but we find ourselves in external linking mode, then we need to remember the -s for invoking the external linker and not treat cmd/link as having the -s anymore. |
CL https://golang.org/cl/10835 mentions this issue. |
Update #10254 Change-Id: I3ddd26607813ca629e3ab62abf87dc5ab453e36f Reviewed-on: https://go-review.googlesource.com/10835 Reviewed-by: Ian Lance Taylor <iant@golang.org>
CL https://golang.org/cl/11695 mentions this issue. |
The text was updated successfully, but these errors were encountered: