[Bug 1592841] Re: FTBFS on ppc64el, blocks updates of all packages depending on krb5, for example CUPS

Sam Hartman hartmans at debian.org
Thu Jun 16 00:17:54 UTC 2016


>>>>> "Till" == Till Kamppeter <1592841 at bugs.launchpad.net> writes:

    Till> Build the package on the system which you have at hand (amd64,
    Till> i386, ...), directing the build output into a file. Search
    Till> through the output to see whther there are any compiler
    Till> warnings and fix them all. With that done the package should
    Till> build on ppc64el.

No, that won't work.
The issue is the ppc64el compiler is behaving differently than the amd64
compiler.
The warning would be an error on any platform.
It's not an warning on amd64, nor is it a warning for ppc64el in debian.

I've spent the time I have here.  On the Debian side I'd definitely take
a patch that added extra extranious initializations to pacify the
compiler.
I recommend that approach to avoid a divergence between ubuntu and
debian.

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

Title:
  FTBFS on ppc64el, blocks updates of all packages depending on krb5,
  for example CUPS

Status in krb5 package in Ubuntu:
  New

Bug description:
  krb5 in Yakkety, version 1.14.2+dfsg-1 does not build on ppc64el and
  so it does not make it from -proposed into release. This blocks
  packages which depend on krb5, like CUPS, from getting from -proposed
  to release, preventing further development on the main platforms
  (amd64, i386, ...) due to the failure on this more exotic platform.

  Other packages depending on krb5 and so suffering the same problem as
  CUPS are: libkdb5, openssh-server, dnsutils, cvs, libkadm5clnt-mit9,
  libkadm5srv-mit9, libdns162, unity-control-center, libdns100.

  cjwatson on IRC, channel #ubuntu-release about this FTBFS and a
  possible fix:

  I suspect it's due to -O3
   Looks like the sort of thing where the compiler does a bit more uninitialised-variable tracking at higher optimisation levels
   Would probably go away at -O2, or somebody could adjust the offending function to pacify the compiler; either way

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1592841/+subscriptions



More information about the foundations-bugs mailing list