public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arsen at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nscd/30709] nscd fails to build with cleanup handler if built with -fexceptions
Date: Wed, 02 Aug 2023 19:51:36 +0000 [thread overview]
Message-ID: <bug-30709-131-rjvJckjRlG@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30709-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30709
Arsen Arsenović <arsen at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |arsen at sourceware dot org
--- Comment #7 from Arsen Arsenović <arsen at sourceware dot org> ---
(In reply to Frederik Schwan from comment #4)
> (In reply to Florian Weimer from comment #3)
> > This is from libgcc_s, right?
> Yes indeed. We don't package static gcc-libs as of now.
>
> Thanks for the explanation, didn't see that it was a static link that failed.
Please don't filter out libgcc.a.
libgcc is a compiler implementation detail, and isn't voluntary like your usual
static library in some 'normal' package. I agree with Andreas in this regard.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-02 19:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 22:34 [Bug build/30709] New: nscd fails to build with cleanup handler freswa at archlinux dot org
2023-07-31 22:47 ` [Bug build/30709] " sam at gentoo dot org
2023-07-31 22:53 ` sam at gentoo dot org
2023-07-31 22:58 ` dilfridge at gentoo dot org
2023-08-01 6:39 ` schwab@linux-m68k.org
2023-08-01 8:03 ` freswa at archlinux dot org
2023-08-01 9:06 ` [Bug nscd/30709] " fweimer at redhat dot com
2023-08-01 9:19 ` [Bug nscd/30709] nscd fails to build with cleanup handler if built with -fexceptions fweimer at redhat dot com
2023-08-01 9:29 ` freswa at archlinux dot org
2023-08-01 14:23 ` fweimer at redhat dot com
2023-08-01 15:10 ` freswa at archlinux dot org
2023-08-02 19:51 ` arsen at sourceware dot org [this message]
2023-08-11 8:54 ` 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-30709-131-rjvJckjRlG@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).