public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/13679] dynamic STT_GNU_IFUNC symbol `strcmp' with pointer equality
Date: Sat, 11 Feb 2012 02:55:00 -0000 [thread overview]
Message-ID: <bug-13679-131-wT1PYmDyBU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13679-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13679
Paul Pluzhnikov <ppluzhnikov at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ppluzhnikov at google dot
| |com
--- Comment #1 from Paul Pluzhnikov <ppluzhnikov at google dot com> 2012-02-11 02:55:10 UTC ---
FWIW,
1. Glibc developers consider fully-static linking a "step child", and your bug
will likely be ignored ...
2. For your stated goal of "static ffmpeg", you don't need to build a
--disable-shared glibc.
The regular build already supplies libc.a. Just do "gcc -static ... -o ffmpeg"
and be done with it.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-02-11 2:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 0:16 [Bug libc/13679] New: " burek021 at gmail dot com
2012-02-11 2:55 ` ppluzhnikov at google dot com [this message]
2012-02-13 0:50 ` [Bug libc/13679] " burek021 at gmail dot com
2012-09-04 23:40 ` [Bug libc/13679] --disable-shared no longer works hjl.tools at gmail dot com
2012-09-25 0:33 ` hjl.tools at gmail dot com
2014-06-27 7:26 ` 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-13679-131-wT1PYmDyBU@http.sourceware.org/bugzilla/ \
--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).