Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.411 (Entity 5.404)
X-RT-Original-Encoding: iso-8859-1
Content-Length: 2718

From George.R.Goffe@seagate.com  Thu Dec 13 20:21:10 2001
Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83])
	by rt-11.mit.edu (8.9.3/8.9.3) with ESMTP id UAA10518
	for <bugs@RT-11.mit.edu>; Thu, 13 Dec 2001 20:21:09 -0500 (EST)
Received: from mr0.sj.mailhost.seagate.com (mr0.sj.mailhost.seagate.com [204.160.183.25])
	by pacific-carrier-annex.mit.edu (8.9.2/8.9.2) with ESMTP id UAA05845
	for <krb5-bugs@mit.edu>; Thu, 13 Dec 2001 20:21:09 -0500 (EST)
Received: from mh0.sj.mailhost.seagate.com (mh0.sj.mailhost.seagate.com [10.26.8.221])
	by mr0.sj.mailhost.seagate.com (8.12.1/8.12.0) with ESMTP id fBE1L8UD018750
	for <krb5-bugs@mit.edu>; Fri, 14 Dec 2001 01:21:08 GMT
Received: from sv-gw2.notes.seagate.com (sv-gw2.stsj.seagate.com [10.26.8.162])
	by mh0.sj.mailhost.seagate.com (8.12.1/8.12.0) with ESMTP id fBE1I1LL002948
	for <krb5-bugs@mit.edu>; Fri, 14 Dec 2001 01:21:01 GMT
Message-Id: <OF7B1AEC0B.6FBA78A6-ON88256B22.00070FAF@notes.seagate.com>
Date: Thu, 13 Dec 2001 17:20:10 -0800
From: George.R.Goffe@seagate.com
To: krb5-bugs@mit.edu
Subject: build problem with krb5-1.2.3-beta3

>Number:         1027
>Category:       krb5-build
>Synopsis:       build problem with krb5-1.2.3-beta3
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    tlyu
>State:          open
>Class:          sw-bug
>Submitter-Id:   unknown
>Arrival-Date:   Thu Dec 13 20:22:00 EST 2001
>Last-Modified:  Thu Apr  4 16:45:05 EST 2002
>Originator:     
>Organization:
>Release:        
>Environment:
>Description:
>How-To-Repeat:
>Fix:
>Audit-Trail:

From: Ken Raeburn <raeburn@MIT.EDU>
To: George.R.Goffe@seagate.com
Cc: krb5-bugs@MIT.EDU
Subject: Re: pending/1027: build problem with krb5-1.2.3-beta3
Date: 13 Dec 2001 22:45:20 -0500

 Sounds like a bug in your gcc snapshot.  You might see if there's a
 more recent version you can get.
 
 If you've gotten the most recent, and the problem is still there, you
 could report it to the gcc maintainers.  There is a transformation
 loop in the SHA-1 code which I could certainly see taking a lot of
 analysis, but the compiler shouldn't take unreasonably long unless
 it's really succeeding in doing a very good job of optimizing and
 needs all that time to do so.
 
 Ken

Responsible-Changed-From-To: gnats-admin->tlyu
Responsible-Changed-By: hartmans
Responsible-Changed-When: Thu Apr  4 16:45:02 2002
Responsible-Changed-Why:

>Unformatted:
Hi there,

I doubt that this is a kerberos problem but I'm seeing a cpu intensive loop
in gcc (snapshot). The build stops in the src/lib/crypto/sha1 directory. I
thought you might have some ideas on how to proceed.

Regards and THANKS for your time,

George...