Bug#165554: __ctype_b symbol no longer available?
At Sun, 20 Oct 2002 14:02:42 -0400,
Daniel Jacobowitz wrote:
> On Mon, Oct 21, 2002 at 01:20:00AM +0900, GOTO Masanori wrote:
> > At Sun, 20 Oct 2002 11:40:37 -0400,
> > Daniel Jacobowitz wrote:
> > > I sent the workaround for this to this list but no one seems to have
> > > noticed it. Jeff, you might want to look at it. It was a forwarded
> > > message from Roland and a pointer to a patch in the Red Hat glibc
> > > packaging. October 7th.
> > >
> > > This will also probably fix the static-binary-NSS-compatibility problem.
> >
> > Where is 'message'? You mean the current upstream cvs is already fixed?
> > We really hope to fix of this issue.
>
> List archives:
> http://lists.debian.org/debian-glibc/2002/debian-glibc-200210/msg00093.html
Thank you for pointing out to me.
I also think the only way to fix is taking off hidden symbols.
I found RedHat's glibc has the 'fix', yes, hidden declaration is just
commented out (I also found RedHat glibc has so many changes). This is
only 'work around' patch as Roland said, but there is no way to avoid
this problem (If some one want to get the explanation about this
issue, I write more in detail).
I've added debian/patches/glibc23-lc-ctype-compat.dpatch in cvs
experimentaly. I've just started to build and test this problem.
I hope all concerns are gone away.
Until sarge, we force to recompile all debian's static libraries for
developers who have such packages, then we remove this patch.
BTW, RedHat glibc patch has libgcc-compat.c for ia64. If debian/ia64
causes this issue, we should also put this patch into our cvs (Jack?).
IPv4/v6 lookup patch is also contained. It seems that investigating
Redhat patch gets more information for other problems.
Regards,
-- gotom
Reply to: