Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA29674; Fri, 1 Dec 95 22:31:05 EST
Received: from DCL.MIT.EDU by MIT.EDU with SMTP
	id AA27696; Fri, 1 Dec 95 22:29:59 EST
Received: by dcl.MIT.EDU (5.0/4.7) id AA00982; Fri, 1 Dec 1995 22:31:03 -0500
Date: Fri, 1 Dec 1995 22:31:03 -0500
From: Theodore Ts'o <tytso@MIT.EDU>
Message-Id: <9512020331.AA00982@dcl.MIT.EDU>
To: omalley@CES.Teradyne.COM
Cc: krb5-bugs@MIT.EDU, omalley@CES.Teradyne.COM
In-Reply-To: Christopher M. O'Malley 's message of Fri, 1 Dec 1995 16:04:55 -0500,
	<199512012104.QAA05217@tiny.icdpcb>
Subject: Re: Problem configuring Krb5
Address: 1 Amherst St., Cambridge, MA 02139
Phone: (617) 253-8091
Content-Length: 821

If you see a message about cross-compiling, and you're not, that
generally means that there's something seriously wrong with the compiler
as you're using it.  

I suspect that in this case that it's the combination of /usr/ucb/cc and
-gO as options.  In any case, using /usr/ucb/cc is completely the wrong
thing to do.  Solaris's UCB compatibility is just good enough to lull
you into thinking that it might be worth wasting your time, and bad
enough that you will end up tearing out your hair wondering why
everything worked until you linked in some library, or some other subtle
failure makes your program start doing all sorts of mysterious things.

The Krb5 tree should work using either suncc or gcc, without any need
for the BSD compatibility libraries or the Solaris BSD compatibility C
compiler.  

							- Ted

