public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "weijun.huang at cs2c dot com.cn" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug ports/13778] New: GLIBC_2.1(MIPS ported)
Date: Tue, 28 Feb 2012 01:29:00 -0000 [thread overview]
Message-ID: <bug-13778-131@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13778
Bug #: 13778
Summary: GLIBC_2.1(MIPS ported)
Product: glibc
Version: 2.12
Status: NEW
Severity: critical
Priority: P2
Component: ports
AssignedTo: unassigned@sourceware.org
ReportedBy: weijun.huang@cs2c.com.cn
CC: carlos@systemhalted.org, roland@gnu.org
Classification: Unclassified
After ported glibc to mips, execut `strings /lib/libc.so.6` and result is 'did
not find GLIBC_2.1/2.1.1/2.1.2/2.1.3', but ALL 2.1* chenged to GLIBC_2.2,
glibc-ports/sysdeps/mips/shlib-versions display '#working mips versions were
never released between 2.0 and 2.2'. What's the problem?
--
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 reply other threads:[~2012-02-28 1:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 1:29 weijun.huang at cs2c dot com.cn [this message]
2012-02-28 3:45 ` [Bug ports/13778] " carlos at systemhalted dot org
2012-02-28 5:02 ` weijun.huang at cs2c dot com.cn
2012-02-28 16:21 ` carlos at systemhalted dot org
2012-02-29 1:58 ` weijun.huang at cs2c dot com.cn
2012-02-29 8:21 ` aj at suse dot de
2012-02-29 9:12 ` weijun.huang at cs2c dot com.cn
2012-02-29 9:21 ` aj at suse dot de
2012-02-29 9:26 ` weijun.huang at cs2c dot com.cn
2012-02-29 9:30 ` weijun.huang at cs2c dot com.cn
2012-02-29 9:33 ` aj at suse dot de
2012-02-29 9:41 ` aj at suse dot de
2012-02-29 14:58 ` carlos at systemhalted dot org
2012-02-29 19:51 ` jsm28 at gcc dot gnu.org
2012-03-01 2:32 ` weijun.huang at cs2c dot com.cn
2012-03-01 2:54 ` weijun.huang at cs2c dot com.cn
2012-03-01 13:56 ` joseph at codesourcery dot com
2012-03-02 1:18 ` weijun.huang at cs2c dot com.cn
2014-06-13 14:08 ` 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-13778-131@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).