Bug#197673: marked as done (libc6: __ctype_b_loc is not properly exported)
Your message dated 27 Aug 2003 14:19:23 +0100
with message-id <1061990362.14192.25.camel@mill.nexus.co.uk>
and subject line libc6: __ctype_b_loc is not properly exported
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 16 Jun 2003 19:27:06 +0000
>From eric@lnxi.com Mon Jun 16 14:26:56 2003
Return-path: <eric@lnxi.com>
Received: from (ash.lnxi.com) [208.177.141.226]
by master.debian.org with smtp (Exim 3.35 1 (Debian))
id 19Rzd1-00025S-00; Mon, 16 Jun 2003 14:26:55 -0500
Received: (qmail 31797 invoked from network); 16 Jun 2003 19:26:38 -0000
Received: from unknown (HELO maxwell.lnxi.com) (192.168.20.129)
by ash.lnxi.com with SMTP; 16 Jun 2003 19:26:38 -0000
Received: from eric by maxwell.lnxi.com with local (Exim 3.35 #1 (Debian))
id 19Rze5-00061u-00
for <submit@bugs.debian.org>; Mon, 16 Jun 2003 13:28:01 -0600
To: submit@bugs.debian.org
Subject: libc6: __ctype_b_loc is not properly exported
From: ebiederman@lnxi.com (Eric W. Biederman)
Date: 16 Jun 2003 13:28:00 -0600
Message-ID: <m3znkhu8jj.fsf@maxwell.lnxi.com>
Lines: 21
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: "Eric W. Biederman" <eric@lnxi.com>
X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (http://amavis.org/)
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-12.3 required=4.0
tests=BAYES_20,HAS_PACKAGE,USER_AGENT_GNUS_UA
autolearn=ham version=2.53-bugs.debian.org_2003_06_10
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_06_10 (1.174.2.15-2003-03-30-exp)
Package: libc6
Version: 2.3.1-17
Severity: important
Programs using <ctype.h> cannot be compiles against 2.3.1-16 or 2.3.1-17 because
__ctype_b_loc is not properly exported from glibc. It only shows up as
__ctype_b_loc@@GLIBC_2.3. I think that is the problem but I am not familiar
enough with symbol versioning to be certain.
A temporary work around is to revert to the libc6-dev 2.2.5-11.5 but it certainly
not satifying.
-- System Information
Debian Release: 3.0
Kernel Version: Linux maxwell.lnxi.com 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 unknown
Versions of the packages libc6 depends on:
ri libdb1-compat 2.1.3-7 The Berkeley database routines [glibc 2.0/2.
---------------------------------------
Received: (at 197673-done) by bugs.debian.org; 27 Aug 2003 13:19:27 +0000
>From pb@nexus.co.uk Wed Aug 27 08:19:24 2003
Return-path: <pb@nexus.co.uk>
Received: from dsl-62-3-66-203.zen.co.uk (crown.nexus.co.uk) [62.3.66.203]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19s0Cq-0003A3-00; Wed, 27 Aug 2003 08:19:24 -0500
Received: from dsl-62-3-66-201.zen.co.uk ([62.3.66.201] helo=mill.nexus.co.uk)
by crown.nexus.co.uk with esmtp (TLS-1.0:RSA_ARCFOUR_MD5:16)
(Exim 4.20)
id 19s0Cp-0003kI-HA
for 197673-done@bugs.debian.org; Wed, 27 Aug 2003 14:19:23 +0100
Subject: Re: libc6: __ctype_b_loc is not properly exported
From: Philip Blundell <pb@nexus.co.uk>
To: 197673-done@bugs.debian.org
Content-Type: text/plain
Message-Id: <1061990362.14192.25.camel@mill.nexus.co.uk>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.3
Date: 27 Aug 2003 14:19:23 +0100
Content-Transfer-Encoding: 7bit
Delivered-To: 197673-done@bugs.debian.org
X-Spam-Status: No, hits=-2.0 required=4.0
tests=BAYES_30,USER_AGENT_XIMIAN
version=2.53-bugs.debian.org_2003_8_17
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_8_17 (1.174.2.15-2003-03-30-exp)
I can't reproduce this problem with glibc 2.3.2, so I am assuming that
the bug is now fixed. Please re-open this report and provide further
details if you are still having trouble.
p.
Reply to: