public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "krejzi at email dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/28786] New: Glibc 2.34 introduces C++ build failures
Date: Sun, 16 Jan 2022 10:18:16 +0000 [thread overview]
Message-ID: <bug-28786-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28786
Bug ID: 28786
Summary: Glibc 2.34 introduces C++ build failures
Product: glibc
Version: 2.34
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: krejzi at email dot com
CC: drepper.fsp at gmail dot com
Target Milestone: ---
When using glibc-2.34 with gcc-11.2.0 to build C++ code, importing some
headers, for example, stdlib.h will throw an error
In file included from /mnt/lfs/tools/include/c++/11.2.0/cstdlib:75,
from
/home/armin/src/pacman/tools/bootstrap/cmake-3.22.1/Source/CursesDialog/ccmake.cxx:6:
/tools/include/stdlib.h:565:5: error: expected initializer before
'__attr_dealloc_free'
565 | __attr_dealloc_free;
| ^~~~~~~~~~~~~~~~~~~
/tools/include/stdlib.h:569:14: error: expected initializer before
'__attr_dealloc'
569 | __THROW __attr_dealloc (reallocarray, 1);
| ^~~~~~~~~~~~~~
There are also issues with other packages and different C headers included
inside C++ code. Please advise on how to proceed here. The problem is not
present in glibc-2.33 and it's triggered by glibc-2.34 upgrade.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-01-16 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 10:18 krejzi at email dot com [this message]
2022-01-17 13:06 ` [Bug libc/28786] " fweimer at redhat dot com
2022-02-04 21:58 ` krejzi at email dot com
2022-02-04 21:59 ` krejzi at email dot com
2022-02-04 22:58 ` 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-28786-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).