[Bug 1417771] Re: juju-core vivid ppc64el fails to build

[Matthias Klose]

the default gccgo in vivid is gccgo-5.  Please check that all needed
patches are available in vivid. the gccgo-go package should be removed,
or just contain symlinks pointing to go-5 and gofmt-5.

** Also affects: gccgo-5 (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: gcc-4.9 (Ubuntu)
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gcc-4.9 in Ubuntu.
https://bugs.launchpad.net/bugs/1417771

Title:
  juju-core vivid ppc64el fails to build

Status in Juju Release Tools:
  Triaged
Status in gcc-4.9 package in Ubuntu:
  Invalid
Status in gccgo-5 package in Ubuntu:
  Incomplete
Status in gccgo-go package in Ubuntu:
  Confirmed
Status in gcc-4.9 source package in Vivid:
  Invalid
Status in gccgo-5 source package in Vivid:
  Incomplete
Status in gccgo-go source package in Vivid:
  Confirmed

Bug description:
  The vivid ppc64el builds are failing. The last success was on
  2015-01.20. their first failure was on 2015-01-23.

  We suspect that golang-go sets the wrong GOARCH in vivid.

  We cannot see the build logs because Lp is a punk. The builds were in the ~juju-package stable and devel ppas
      https://launchpad.net/~juju-packaging/+archive/ubuntu/stable/+packages
      https://launchpad.net/~juju-packaging/+archive/ubuntu/devel/+packages?field.name_filter=juju-core&field.status_filter=superseded&field.series_filter=vivid

  Using the source packages at
      https://launchpad.net/~juju-packaging/+archive/ubuntu/stable/+packages?field.name_filter=juju-core&field.status_filter=published&field.series_filter=vivid

  When we build in a vivid ppc64el container on (stilson-07). the build
  failed at the first call to use the built juju. The first call is to
  generate the man pages using "juju version" and "juju help commands"
  debian/rules sets the GOPATH  and then adds the GOPATH/bin to PATH.
  The build binaries were placed in $GOPATH/bin/linux__ppc64le, not
  $GOPATH/bin!

  The "dpkg --print-architecture" for both the host and the container are  "ppc64el".
  The host'ss "go env" shows GOARCH="ppc64"
  The container's "go env" shows GOARCH="ppc64le"

  I can contrive a successful build doing this
      GOARCH=ppc64 dpkg-buildpackage -us -uc

  So we could change debian/rules, but we first need to understand if
  GOARCH for vivid ppc64el is sane.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-release-tools/+bug/1417771/+subscriptions