Skip Menu |

Download (untitled) / with headers
text/plain 2.6KiB
From Tue Sep 18 18:11:57 2001
Received: from (FORT-POINT-STATION.MIT.EDU [])
by (8.9.3/8.9.3) with ESMTP id SAA19605
for <>; Tue, 18 Sep 2001 18:11:57 -0400 (EDT)
Received: from ( [])
by (8.9.2/8.9.2) with SMTP id SAA23402
for <>; Tue, 18 Sep 2001 18:11:56 -0400 (EDT)
Received: (qmail 71339 invoked by uid 1001); 18 Sep 2001 22:11:47 -0000
Message-Id: <>
Date: 18 Sep 2001 22:11:47 -0000
Subject: processing of --with-cc defaults to cc not gcc first
X-Send-Pr-Version: 3.99

Show quoted text
>Number: 992
>Category: krb5-build
>Synopsis: processing of --with-cc defaults to cc not gcc first
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: tlyu
>State: analyzed
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Tue Sep 18 18:13:00 EDT 2001
>Last-Modified: Tue Sep 18 22:58:00 EDT 2001
>Originator: Sean Chittenden

Show quoted text
>Release: krb5-1.2.2

System: SunOS Generic_106541-14 sun4u sparc SUNW,Ultra-5_10
Architecture: sun4

Show quoted text
When trying to configure kerberos, configure can't find a compiler
if the compiler is stored in a non-default location.
Show quoted text
Install gcc into a non-standard directory that is still in your path
Try and compile kerberos
Show quoted text
setenv CC gcc

./configure works like a charm... why it needs that extra hint I don't
know, but it's pretty critical to get everything kicked off. The thing
that really bugs me, however, is I've compiled almost every piece of
software under the sun on a Sun and haven't had a problem except with
krb5. gcc is in my path (/usr/SD/bin/gcc) and which reports it in the
correct place.
Show quoted text

State-Changed-From-To: open-analyzed
State-Changed-By: tlyu
State-Changed-When: Tue Sep 18 22:57:03 2001

We'll have to fix this nastiness eventually.

From: Tom Yu <tlyu@MIT.EDU>
Cc: krb5-bugs@MIT.EDU
Subject: Re: krb5-build/992: ./configure can't find a working compiler if gcc in non-standard location
Date: Tue, 18 Sep 2001 22:56:16 -0400 (EDT)

Thanks for the bug report; we've got some rather strange code that
doesn't call AC_PROG_CC directly, but rather jumps through some odd
hoops first, which ends up defaulting the compiler to cc rather than
trying gcc first. This is tied up with the whole --with-cc=foo
situation. We'll look into fixing it in a future release.

Show quoted text
Fixed on trunk, since we're now using AC_PROG_CC.