Bug#776401: [pkg-golang-devel] Bug#776401: Bug#776401: Bug#776401: Bug#776401: [Pkg-golang-devel] Bug#776401: Bug#776401: src:golang: Set CGO_ENABLED for all platforms

2016-03-01 Thread Michael Hudson-Doyle
On 16 February 2016 at 11:13, Tianon Gravi wrote: > On 11 February 2016 at 17:50, Michael Hudson-Doyle > wrote: >> It's the standard library packages, GOARCH=arm go install runtime is >> going to try to create $GOROOT/pkg/linux_arm/runtime.a. > >

Bug#776401: [pkg-golang-devel] Bug#776401: Bug#776401: Bug#776401: [Pkg-golang-devel] Bug#776401: Bug#776401: src:golang: Set CGO_ENABLED for all platforms

2016-02-15 Thread Tianon Gravi
On 11 February 2016 at 17:50, Michael Hudson-Doyle wrote: > I'm not sure I want to be the one that takes that one upstream. Totally fair -- I just meant that it's something that probably ought to be taken upstream, not necessarily that I expected you to do so; sorry

Bug#776401: [pkg-golang-devel] Bug#776401: Bug#776401: [Pkg-golang-devel] Bug#776401: Bug#776401: src:golang: Set CGO_ENABLED for all platforms

2016-02-11 Thread Tianon Gravi
On 4 February 2016 at 16:56, Michael Hudson-Doyle wrote: > I guess it could be fixed by going back to building lots of > golang-$GOOS-$GOARCH packages, but somehow that doesn't seem very > appealing, it would be nicer to allow the go install command to work > (which

Bug#776401: [pkg-golang-devel] Bug#776401: Bug#776401: [Pkg-golang-devel] Bug#776401: Bug#776401: src:golang: Set CGO_ENABLED for all platforms

2016-02-11 Thread Michael Hudson-Doyle
On 12 February 2016 at 12:44, Tianon Gravi wrote: > On 4 February 2016 at 16:56, Michael Hudson-Doyle > wrote: >> I guess it could be fixed by going back to building lots of >> golang-$GOOS-$GOARCH packages, but somehow that doesn't seem very >>

Bug#776401: [pkg-golang-devel] Bug#776401: [Pkg-golang-devel] Bug#776401: Bug#776401: src:golang: Set CGO_ENABLED for all platforms

2016-02-05 Thread Hilko Bengen
* Michael Hudson-Doyle: > I guess it could be fixed by going back to building lots of > golang-$GOOS-$GOARCH packages, but somehow that doesn't seem very > appealing, Another option may be building *one* extra package that contains the stdlib and whatever bits may be necessary for building for

Bug#776401: [pkg-golang-devel] Bug#776401: [Pkg-golang-devel] Bug#776401: Bug#776401: src:golang: Set CGO_ENABLED for all platforms

2016-02-04 Thread Michael Hudson-Doyle
On 4 February 2016 at 02:12, Hilko Bengen wrote: > * Tianon Gravi: > >> I'm not positive whether all were required for this to work, but given >> that it _did_ work, I think this is in the realm of possible with the >> changes of Go 1.5 and am inclined to close this bug as

Bug#776401: [Pkg-golang-devel] Bug#776401: Bug#776401: src:golang: Set CGO_ENABLED for all platforms

2016-02-03 Thread Tianon Gravi
On 7 March 2015 at 09:21, Hilko Bengen wrote: > As far as I can see, it does not. The only notable change is that > cgo.a files are installed for more than one architecture. > >> Also, what's the impact on the future Go 1.5, especially the new, >> simpler cross-compile[1] that

Bug#776401: [Pkg-golang-devel] Bug#776401: Bug#776401: src:golang: Set CGO_ENABLED for all platforms

2016-02-03 Thread Hilko Bengen
* Tianon Gravi: > I'm not positive whether all were required for this to work, but given > that it _did_ work, I think this is in the realm of possible with the > changes of Go 1.5 and am inclined to close this bug as "fixed" -- > thoughts? :) Unfortunately, it's not that easy. :-( Last time I