libc resolver problem solved (critical bug)

To: Gergely Madarasz <gorgo@caesar.elte.hu>
Cc: debian-devel@lists.debian.org
Subject: libc resolver problem solved (critical bug)
From: Matthias Klose <doko@cs.tu-berlin.de>
Date: Thu, 19 Nov 1998 10:35:24 +0100 (MET)
Message-id: <[🔎] 13907.58883.255924.823319@bolero>
In-reply-to: <[🔎] Pine.A32.3.96.981118115708.56798C-100000@caesar.power.elte.hu>
References: <[🔎] Pine.A32.3.96.981118115708.56798C-100000@caesar.power.elte.hu>

Gergely Madarasz writes:
 > Hello!
 > 
 > (current 2.0.7u-5: Compiled by GNU CC version egcs-2.90.27 980315
 > (egcs-1.0.2 release).)

 > Ps. this is very serious, egcs miscompiles libc!!!!!!!!!!!

Yes, it would be serious, if this is the case for egcs-2.91.58 as
well. Is this the case?

Reply to:

Follow-Ups:
- Re: libc resolver problem solved (critical bug)
  - From: Gergely Madarasz <gorgo@caesar.elte.hu>
- glibc recompiling was Re: libc resolver problem solved (critical bug)
  - From: Dale Scheetz <dwarf@polaris.net>

References:
- libc resolver problem solved (critical bug)
  - From: Gergely Madarasz <gorgo@caesar.elte.hu>

Prev by Date: Re: screen / ncurses problem in slink.
Next by Date: Re: Problem: installing hamm on laptop
Previous by thread: Re: libc resolver problem solved (critical bug)
Next by thread: Re: libc resolver problem solved (critical bug)
Index(es):
- Date
- Thread