From: Kbwms AT aol DOT com Message-ID: <1a5.18a6e270.2c853164@aol.com> Date: Mon, 1 Sep 2003 19:33:56 EDT Subject: Re: Bug in log10l in libstdcxx.a To: djgpp-workers AT delorie DOT com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_1a5.18a6e270.2c853164_boundary" X-Mailer: 8.0 for Windows sub 6015 Reply-To: djgpp-workers AT delorie DOT com --part1_1a5.18a6e270.2c853164_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 9/1/2003 6:17:24 PM Eastern Standard Time, dj AT delorie DOT com writes: > >There are no versions of log10l() anywhere else in the lib directory. > > Sounds like it's not our problem, then. If you want to pursue this, > see http://gcc.gnu.org/ for bug reporting instructions. > My only concern is that our users know about the problem. I've been finding bugs in glibc-2.3.2 C code and that's a lot more fun that trying to wander through the gnu.org tangle. --part1_1a5.18a6e270.2c853164_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable In a message dated 9/1/2003 6:17:24 PM Eastern Standard=20= Time, dj AT delorie DOT com writes:

>There are no versions of log10l() anywhere else in the=20= lib directory.

Sounds like it's not our problem, then. If you want to pursue this, see http://gcc.gnu.org/ for bug reporting instructions.

My only concern is that our users know about the problem. I've been fi= nding bugs in glibc-2.3.2 C code and that's a lot more fun that trying to wa= nder through the gnu.org tangle. --part1_1a5.18a6e270.2c853164_boundary--