public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "simon.chopin at canonical dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/31928] New: glibc doesn't compile if the compiler already define _FORTIFY_SOURCE
Date: Tue, 25 Jun 2024 15:06:57 +0000	[thread overview]
Message-ID: <bug-31928-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=31928

            Bug ID: 31928
           Summary: glibc doesn't compile if the compiler already define
                    _FORTIFY_SOURCE
           Product: glibc
           Version: 2.39
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: simon.chopin at canonical dot com
                CC: carlos at redhat dot com
  Target Milestone: ---

In Ubuntu, GCC has been modified to define _FORTIFY_SOURCE in the preprocessor
driver, resulting in failures to build glibc, with the following error (with
--disable-werror):

syslog.c: In function ‘__vsyslog_internal’:
syslog.c:95:30: error: inlining failed in call to ‘always_inline’ ‘syslog’:
function not inlinable
   95 | ldbl_strong_alias (__syslog, syslog)

We're shipping a patch to adress this in 2.39, I still need to rebase it and
clean it up:

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/glibc/tree/debian/patches/ubuntu/fix-fortify-source.patch

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2024-06-25 15:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 15:06 simon.chopin at canonical dot com [this message]
2024-06-26  7:14 ` [Bug build/31928] " fweimer at redhat dot com
2024-06-26  7:48 ` sam at gentoo dot org
2024-06-26  8:30 ` simon.chopin at canonical dot com
2024-06-26  8:36 ` fweimer at redhat dot com
2024-06-26 11:48 ` adhemerval.zanella at linaro dot org
2024-06-26 19:17 ` fweimer at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-31928-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).