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] GLIBC_2.1(MIPS ported)
Date: Wed, 29 Feb 2012 01:58:00 -0000 [thread overview]
Message-ID: <bug-13778-131-JamZy4bHrU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13778-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13778
--- Comment #4 from 黄卫军 <weijun.huang at cs2c dot com.cn> 2012-02-29 01:58:16 UTC ---
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > Could you please describe your problem in more detail?
> >
> > < Detail: port glibc(with mips patch -- ports) to MIPS, rpm installed then find
> > /lib/libc.so.6 did not GLIBC_2.1/2.1.1/2.1.2/2.1.3, such as popen@@GLIBC_2.2.
> > If not patch mips with ports, `nm /lib/libc.so.6|grep popen` will find
> > popen@@GLIBC_2.1. Other all symbols GLIBC_2.1* was changed to GLIBC_2.2. I find
> > '#working mips versions were never released between 2.0 and 2.2' in file
> > 'ports/sysdeps/mips/shlib-versions'. Q: How to fix it? May be not 2.1*?
>
> Why do you need to fix it?
>
> Are you getting an error running an old application?
>
> What error are you seeing?
======
More details:
1, my machine arch is MIPS, port glibc to MIPS must patch(MIPS patch), ported
glibc(with MIPS patch) to MIPS, execute "strings /lib/libc.so.6|grep GLIBC"
then did not find version GLIBC_2.1, in other words, symbol version changed
from GLIBC_2.1 to GLIBC_2.2, such as fclose.
2, after that, test LSB, test mips item modify from i386, and result is
--------
Did not find fclose (GLIBC_2.1) in libc.so.6
check function: fdopen (GLIBC_2.1) in libc.so.6
Warning: did not find version tag GLIBC_2.1 in library
available version is GLIBC_2.2
Warning: did not find version tag GLIBC_2.1 in library
available version is GLIBC_2.0
--------
then FAIL once, etc.
In order to PASS all, question is which one should I do:
1) modify MIPS patch to support version GLIBC_2.1?
2) or, modify LSB check from GLIBC_2.1 to GLIBC_2.2?
(e.g. check fclose version from GLIBC_2.1 to GLIBC_2.2)
======
--
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-29 1:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 1:29 [Bug ports/13778] New: " weijun.huang at cs2c dot com.cn
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 [this message]
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-JamZy4bHrU@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).