public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/11177] LD_AUDIT doesn't work with shared libraries containing no code
Date: Thu, 28 Jan 2010 08:17:00 -0000 [thread overview]
Message-ID: <20100128081724.29433.qmail@sourceware.org> (raw)
In-Reply-To: <20100115110434.11177.andris.zeila@accenture.com>
------- Additional Comments From drepper at redhat dot com 2010-01-28 08:17 -------
(In reply to comment #5)
> Either dynamic linker should reject linking such libraries or LD_AUDIT should
> accept them.
That's nonsense. There are simply different requirements. Just fix the DSOs
and be done with it. The fact that whatever tests the debian system performs
aren't showing problems doesn't mean anything. Special casing just creates
problems.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |WONTFIX
http://sourceware.org/bugzilla/show_bug.cgi?id=11177
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-01-28 8:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 11:04 [Bug libc/11177] New: " andris dot zeila at accenture dot com
2010-01-15 11:05 ` [Bug libc/11177] " andris dot zeila at accenture dot com
2010-01-15 11:05 ` andris dot zeila at accenture dot com
2010-01-15 12:27 ` kirill at shutemov dot name
2010-01-20 2:04 ` drepper at redhat dot com
2010-01-21 15:23 ` eero dot tamminen at nokia dot com
2010-01-27 9:37 ` eero dot tamminen at nokia dot com
2010-01-28 8:17 ` drepper at redhat dot com [this message]
2010-02-08 9:03 ` eero dot tamminen at nokia dot com
[not found] <bug-11177-131@http.sourceware.org/bugzilla/>
2014-06-30 20:22 ` fweimer at redhat dot com
2014-07-01 14:42 ` paul_woegerer at mentor 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=20100128081724.29433.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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).