[Bug 1867316] Re: FTFBS in Focal armhf/ppc64/s390x

[Christian Ehrhardt ]

Chances are high that this -fixed was brought in via a bug/discussion,
lets check the changelog to find it.

    9 gcc-9 (9.3.0-1) unstable; urgency=medium                                         
...
   16   * Stop shipping the include-fixed directory.                                   
...
   20  -- Matthias Klose <doko at debian.org>  Thu, 12 Mar 2020 15:24:59 +0100

Arr I should learn to read versions more in depth, it in fact IS
different:

ii  libgcc-9-dev:amd64 9.2.1-30ubuntu2 amd64        GCC support library (development files)
vs
ii  libgcc-9-dev:s390x 9.3.0-1ubuntu2 s390x        GCC support library (development files)

So this change broke us and probably many things.
Unless there is a twist to it I'm yes missing.
Marking it critical for gcc-9 which is the source this built from and assigning to doko who did the uploads.

** Changed in: glibc (Ubuntu)
       Status: New => Confirmed

** Changed in: gcc-9 (Ubuntu)
       Status: New => Confirmed

** Changed in: glibc (Ubuntu)
       Status: Confirmed => Invalid

** Changed in: linux (Ubuntu)
       Status: Incomplete => Invalid

** Changed in: gcc-9 (Ubuntu)
   Importance: Undecided => Critical

** Changed in: gcc-9 (Ubuntu)
     Assignee: (unassigned) => Matthias Klose (doko)

** Summary changed:

- FTFBS in Focal armhf/ppc64/s390x
+ Almost global FTFBS due to dropping include-fixed dir in 9.3.0-1

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

Title:
  Almost global FTFBS due to dropping include-fixed dir in 9.3.0-1

Status in chrony package in Ubuntu:
  Invalid
Status in gcc-9 package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This seems an almost global FTBFS with anything that includes limits.h

  $ cat > test.c << EOF
  > /*
  > * Test FTBFS 1867316
  > */
  >
  > #include <limits.h>
  > EOF
  ubuntu at focal-ftbfs:~/chrony-3.5$ gcc -c test.c
  In file included from test.c:5:
  /usr/include/limits.h:124:26: error: no include path in which to search for limits.h
    124 | # include_next <limits.h>
        | ^

  Interestingly this fails on armhf/ppc64/s390x but works on x86.

  
  --- started as a chrony FTBFS despite tetsing a few hours before ---

  For bug 1866753 we built this yesterday in a proposed PPA and things worked!
  Now today on the final upload it failed to build on armhf/ppc64/s390x.

  In file included from /usr/include/powerpc64le-linux-gnu/sys/param.h:26,
                   from /usr/include/resolv.h:56,
                   from nameserv.c:34:
  /usr/include/limits.h:124:26: error: no include path in which to search for limits.h
    124 | # include_next <limits.h>
        |                          ^
  make[1]: *** [Makefile:108: nameserv.o] Error 1

  The same error on all of them.

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