X-pop3-spooler: POP3MAIL 2.1.0 b 4 980420 -bs-
Date: Mon, 5 Oct 1998 16:55:15 -0400 (EDT)
From: Jason Ahrens <jahrens AT magma DOT ca>
To: Marc Lehmann <pcg AT goof DOT com>
Subject: Re: pgcc1.1 installation
In-Reply-To: <19981005220405.D300@cerebro.laendle>
Message-ID: <Pine.BSI.3.96.981005164923.12997A-100000@shell.magma.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Marc Lehmann <pcg AT goof DOT com>
Status: RO
X-Status: A
Content-Length: 934
Lines: 28

On Mon, 5 Oct 1998, Marc Lehmann wrote:

> glibc in itself isn't a problem, maybe you have installed a broken or an
> alpha version?

I don't beleive so. I installed 2.0.6 which I had just downloaded from a
GNU mirror.

> That looks like filesystem corruption or like severe hardwrare problem. It
> definitely hasn't anything to do with pgcc. Are you overclocking your
> machine?

No. fsck's are comming up clean, and for hardware, unless something  has
gone bad very recently...

> Or have you compiled other things yourself with a broken compiler? Which
> compiler did you use to build pgcc?

As of yet, no. I was using pgcc 1.1 linked with libc5 to compile pgcc 1.1
linked with glibc...  

Maybe I should download a pgcc linked to glibc if one is available and try
again? The pgcc page lists 1.0.3 as most recent precompiled version. 

Or maybe the glibc tests wern't correct when they said all was well after
compiling it?

Jason