Hi,
On 13/06/17 18:39, Tianon Gravi wrote:
> On 7 June 2017 at 02:23, Mathieu Malaterre wrote:
>> Are you saying that the patch is more complex than just
>> s/mipsn64/mips64el/ ? Or are you saying you do not want to maintain
>> such patch until upstream add an alias for
On 7 June 2017 at 02:23, Mathieu Malaterre wrote:
> Are you saying that the patch is more complex than just
> s/mipsn64/mips64el/ ? Or are you saying you do not want to maintain
> such patch until upstream add an alias for mips64el ?
Yes, the patch is more complex than simply
Hi Tianon,
> The main issue with getting it in essentially boils down to gccgo and
> upstream Go disagreeing on the GOARCH for mips64el (gccgo uses
> "mipsn64"[0]), which makes bootstrapping difficult.
>
> [0]: https://groups.google.com/d/topic/golang-nuts/waTy56I_KWQ/discussion
Are you saying
affects 815998 + golang-go
forcemerge 815998 841645
thanks
On 21 October 2016 at 09:58, Harry Prevor wrote:
> But the Debian versions of these packages don't have mips64el support, even
> though this is a new Debian port. Can mips64el packages be built and added to
> the
Package: golang-go
Version: 2:1.7~1
Severity: normal
Dear Maintainer,
Since golang 1.6, upstream Go supports mips64 and mips64el:
https://golang.org/doc/install/source
But the Debian versions of these packages don't have mips64el support, even
though this is a new Debian port. Can mips64el
5 matches
Mail list logo