1993-03-10 - Re: Questions about PGP 2.2 compilation messages

Header Data

From: Eric Fogleman <Eric.Fogleman@analog.com>
To: i6t4@jupiter.sun.csd.unb.ca
Message Hash: 81f039e85009a706c5fb3d6af68ca0c964815f82f40e0836f6c1525ea07f4bf7
Message ID: <9303100125.AA10660@ack.adstest.analog.com>
Reply To: N/A
UTC Datetime: 1993-03-10 01:32:26 UTC
Raw Date: Tue, 9 Mar 93 17:32:26 PST

Raw message

From: Eric Fogleman <Eric.Fogleman@analog.com>
Date: Tue, 9 Mar 93 17:32:26 PST
To: i6t4@jupiter.sun.csd.unb.ca
Subject: Re: Questions about PGP 2.2 compilation messages
Message-ID: <9303100125.AA10660@ack.adstest.analog.com>
MIME-Version: 1.0
Content-Type: text/plain


I recently compiled _pgp2.1_ on my sun4 and had a similar problem...  I
got a binary that seemed to work, but I got a list of warnings.

In my case, the program actually had a bug in it; it was trying to
compare an unsigned character variable (8 bits) for maximum path length
to 256 (nine bits) as defined in the source code.  I asked around on
the list and I got the same sort of responses you did...

I ended up redefining and changing the compare statement to make the
compiler happy and still get the intended code...

So, pgp may not be entirely bug free...  The sun4 compiler may be more
conscientious about flagging things.  I'd suggest looking through the
source to see if there's something simple.  In my case, it was.

Let me know how you fare; I'll be going through the same thing shortly...

Eric Fogleman