FTBFS with glibc 2.34

Bug #1951665 reported by Sergio Durigan Junior
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
opentracing-cpp (Ubuntu)
Fix Released
High
Sergio Durigan Junior

Bug Description

Building with glibc 2.34 leads to a compilation error because SIGSTKSZ
is not a constant anymore. From glibc's NEWS file:

  * Add _SC_MINSIGSTKSZ and _SC_SIGSTKSZ. When _SC_SIGSTKSZ_SOURCE or
     _GNU_SOURCE are defined, MINSIGSTKSZ and SIGSTKSZ are no longer
     constant on Linux. MINSIGSTKSZ is redefined to sysconf(_SC_MINSIGSTKSZ)
     and SIGSTKSZ is redefined to sysconf (_SC_SIGSTKSZ).

Here's the error:

  In file included from /usr/include/signal.h:328,
                   from /<<PKGBUILDDIR>>/3rd_party/include/opentracing/catch2/catch.hpp:6456,
                   from /<<PKGBUILDDIR>>/test/string_view_test.cpp:5:
  /<<PKGBUILDDIR>>/3rd_party/include/opentracing/catch2/catch.hpp:6631:45: error: size of array ‘altStackMem’ is not an integral constant-expression
   6631 | char FatalConditionHandler::altStackMem[SIGSTKSZ] = {};
        | ^~~~~~~~

Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :
Changed in opentracing-cpp (Ubuntu):
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package opentracing-cpp - 1.6.0-2ubuntu1

---------------
opentracing-cpp (1.6.0-2ubuntu1) jammy; urgency=medium

  * d/p/fix-ftbfs-glibc-2.34.patch: Fix FTBFS with glibc 2.34.
    (LP: #1951665)

 -- Sergio Durigan Junior <email address hidden> Fri, 19 Nov 2021 20:02:14 -0500

Changed in opentracing-cpp (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.