If I remember correctly, the stripping on gc built binaries was only
problematic on armhf - the general upstream advice was 'don't strip - it
breaks stuff' so we disabled it.
That was with 1.1 - things may have moved on with 1.2 of golang
--
You received this bug notification because you are a
On Mon, May 19, 2014 at 11:13 AM, James Page james.p...@ubuntu.com
wrote:
If I remember correctly, the stripping on gc built binaries was only
problematic on armhf - the general upstream advice was 'don't strip - it
breaks stuff' so we disabled it.
That was with 1.1 - things may have moved
Bug 1200255 is related. The same issue happens with the go toolchain. We
ended up specifically not stripping binaries in juju, and I think other
go binaries need to be built this way also.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
On Mon, May 12, 2014 at 02:25:31PM -, Robie Basak wrote:
Bug 1200255 is related. The same issue happens with the go toolchain.
It's not the same issue. In my tests here, I am able to strip gc binaries
(with carefully-constructed commandlines) in a way that retains all of the
go symbols and
** Changed in: golang (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang in Ubuntu.
https://bugs.launchpad.net/bugs/1318027
Title:
Go binaries cannot be stripped
To manage
You've retitled this bug report to say that go binaries cannot be
stripped, but please note that in my report I stated that debugging
symbols *can* be removed from binaries built with GC.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
