This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug go/63565] New: please document that (and why) Go binaries should not be stripped
- From: "doko at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 16 Oct 2014 21:54:27 +0000
- Subject: [Bug go/63565] New: please document that (and why) Go binaries should not be stripped
- Auto-submitted: auto-generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63565
Bug ID: 63565
Summary: please document that (and why) Go binaries should not
be stripped
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
Assignee: ian at airs dot com
Reporter: doko at gcc dot gnu.org
CC: cmang at google dot com
please document that (and why) Go binaries should not be stripped.
the standard action for distributions is to strip binaries unconditionally,
however there are some issues seen when binaries are stripped. The Debian and
Ubuntu builds strip libgo itself, which seems to work fine, but stripping some
applications leads to errors. So it would be good to know which information
can be safely stripped, and which not.