[Bug ports/13778] GLIBC_2.1(MIPS ported)

["weijun.huang at cs2c dot com.cn" <sourceware-bugzilla at sourceware dot org>]

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.