This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


http://sourceware.org/bugzilla/show_bug.cgi?id=13778

éåå <weijun.huang at cs2c dot com.cn> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |

--- Comment #6 from éåå <weijun.huang at cs2c dot com.cn> 2012-02-29 09:12:13 UTC ---
(In reply to comment #5)
> There is a bug in your old glibc if it needs GLIBC 2.1. There has never been a
> working glibc release with version 2.1 in it and thus if you have it, something
> went wrong in your previous installation.
> 
> If LSB demands GLIBC_2.1, then LSB is wrong and needs to be fixed.

My glibc version is 2.12.1(5/2010), I think it not old, the newest is
2.15(2/2012) for fedora18. 
such as symbol popen only two versions: GLIBC_2.0 and GLIBC_2.1 provide by
glibc. Ported glibc(mips patch), symbol popen versions is GLIBC_2.0 and
GLIBC_2.2.

I think either modify LSB check popen version GLIBC_2.2(not GLIBC_2.1) or
modify glibc mips patch to support GLIBC_2.1.
I like the latter, but do not what to do.

-- 
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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]