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

[Curtis Hovey]

There has been a lot confusion about this bug. As the reporter, I am
happy to say vivid packaging (or cloud/builder images) were fixed last
week. Without any changes to juju packaging. Launchpad  and lxc can
again built vivid ppc64el packages without explicitly setting the GOARCH
to match the dpkg architecture.

And to be clear, this issue was only ever about a mismatch of deb
architecture which caused gccgo to think it is cross-compiling. The
binaries worked fine if you could find them.

These packages are among the changes seen in my stale container when I issued the dist-upgrade.
     g++-4.9 gcc-4.9 gcc-4.9-base gcc-5-base gccgo gccgo-5 gccgo-go libgo5 libgo7

We can see from Lp that the fix arrived on or before 2015-02-17.

-- 
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:
  Invalid
Status in gcc-4.9 package in Ubuntu:
  Invalid
Status in gccgo-5 package in Ubuntu:
  Fix Released
Status in gccgo-go package in Ubuntu:
  Fix Released
Status in gcc-4.9 source package in Vivid:
  Invalid
Status in gccgo-5 source package in Vivid:
  Fix Released
Status in gccgo-go source package in Vivid:
  Fix Released

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