OtherBugsDependingO 611
nThis:
Need a clear decision on the glibc symbol versions required by the LSB.
Currently there are a small number of actual or potential GLIBC_2.3.3 symbols,
all of which have earlier versions in the library as well. There are also a
couple of GLIBC_2.3.4 symbols, one of which is a new symbol. It's believed
there are some distros that will not move beyond GLIBC_2.3.2 symbols in the near
future, so this might be a restriction. Here's the currently known list:
* all except s390, s390x: _sys_siglist is now GLIBC_2.3.3
* ppc64: _ _sigsetjmp, _longjmp, _setjmp, longjmp, siglongjmp, getcontext,
setcontext,swapcontext were changed to version GLIBC_2.3.4 to match a change to
an underlying data structure.
* ppc64 also changes nftw, nftw64 to GLIBC_2.3.3 and regexec to GLIBC_2.3.4.
Note that the same version changes exist for all LSB archictectures in upstream
glibc but were not picked up for the others in LSB 3.
* ppc32: getcontext, makecontext, setcontext, swapcontext were changed to
GLIBC_2.3.3 to match a change to an underlying data structure. There's also a
set of GLIBC_2.3.4 versions of the same interfaces!
It's not out of the question that LSB 3 could stay at GLIBC_2.3.2 or lower,
excepting maybe the ppc context stuff (see also Bug 809 on that one)
--
Configure bugmail: http://bugs.linuxbase.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.