Skip Menu |
 

Download (untitled) / with headers
text/plain 2.2KiB
From klehigh@gauley.ucs.indiana.edu Tue Jun 10 17:37:50 2003
Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by krbdev.mit.edu (8.9.3) with ESMTP
id RAA21275; Tue, 10 Jun 2003 17:37:49 -0400 (EDT)
Received: from julesburg.uits.indiana.edu (julesburg.uits.indiana.edu [129.79.1.75])
by fort-point-station.mit.edu (8.12.4/8.9.2) with ESMTP id h5ALbnj9025829
for <krb5-bugs@mit.edu>; Tue, 10 Jun 2003 17:37:49 -0400 (EDT)
Received: from logchain.uits.indiana.edu (logchain.uits.indiana.edu [129.79.1.77])
by julesburg.uits.indiana.edu (8.12.9/8.12.9/IUPO) with ESMTP id h5ALbkib029689
for <krb5-bugs@mit.edu>; Tue, 10 Jun 2003 16:37:46 -0500 (EST)
Received: from gauley.ucs.indiana.edu (gauley.ucs.indiana.edu [129.79.5.61])
by logchain.uits.indiana.edu (8.12.9/8.12.9/IUPO) with ESMTP id h5ALbl8n028697
for <krb5-bugs@mit.edu>; Tue, 10 Jun 2003 16:37:47 -0500 (EST)
Received: (from klehigh@localhost)
by gauley.ucs.indiana.edu (8.11.7+Sun/8.11.7) id h5ALZYO20613;
Tue, 10 Jun 2003 16:35:34 -0500 (EST)
Date: Tue, 10 Jun 2003 16:35:34 -0500 (EST)
Message-Id: <200306102135.h5ALZYO20613@gauley.ucs.indiana.edu>
To: krb5-bugs@mit.edu
From: klehigh@iupui.edu
Reply-To: klehigh@iupui.edu
Cc:
X-send-pr-version: 3.99


Show quoted text
>Submitter-Id: net
>Originator: Keith Lehigh
>Organization: Indiana University

Show quoted text
>Confidential: no
>Synopsis: On Solaris 8 configure script can't find gcc
>Severity: non-critical
>Priority: low
>Category: krb5-build
>Class: support
>Release: krb5-1.2.8
>Environment:

System: SunOS gauley 5.8 Generic_108528-20 sun4u sparc SUNW,Sun-Fire-280R
Architecture: sun4

Show quoted text
>Description:
Running configure in top level of src dir ( krb5-1.2.8/src ) it can't find gcc unless I use "--with-cc=/path/to/gcc" or I set an environment variable of $CC=/path/to/gcc . My gcc is located at /usr/local/bin/gcc and this is in my path. I have compiled other source on this machine, and gcc is always found. I realize this may be on purpose, but I didn't see anything in the documentation. Most folks should be able to fix this (like I did), but I thought maybe this should be noted somewhere? Or maybe people should just use the configure options.
Show quoted text
>Fix:
Insufficient knowledge to correct configure script.
To: rt@krbdev.mit.edu
Cc: krb5-prs@mit.edu
Subject: Re: [krbdev.mit.edu #1587] On Solaris 8 configure script can't find gcc
From: Sam Hartman <hartmans@mit.edu>
Date: Tue, 10 Jun 2003 18:12:03 -0400
RT-Send-Cc:


You can use the --with-cc= argument to configure to tell it where to
find gcc.
Date: Wed, 11 Jun 2003 11:56:22 -0500 (EST)
From: Keith Lehigh <klehigh@iupui.edu>
To: Sam Hartman via RT <rt-comment@krbdev.mit.edu>
Subject: Re: [krbdev.mit.edu #1587] On Solaris 8 configure script can't find gcc
RT-Send-Cc:
Indeed, and I was able to successfully compile it using both --with-cc=
and setting an environment variable for "CC", however, I was curious as to
why your configure script is unable to find a common compiler in a common
location. Is this a philosophical decision, or just a function/feature
that hasn't been included yet?
Thanks,

Keith

On Tue, 10 Jun 2003, Sam Hartman via RT wrote:

Show quoted text
>
>
> You can use the --with-cc= argument to configure to tell it where to
> find gcc.
>
>
To: rt@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #1587] On Solaris 8 configure script can't find gcc
From: Sam Hartman <hartmans@mit.edu>
Date: Wed, 11 Jun 2003 17:32:46 -0400
RT-Send-Cc:
Show quoted text
>>>>> "klehigh@iupui" == klehigh@iupui edu via RT <rt-comment@krbdev.mit.edu> writes:

klehigh@iupui> Indeed, and I was able to successfully compile it
klehigh@iupui> using both --with-cc= and setting an environment
klehigh@iupui> variable for "CC", however, I was curious as to why
klehigh@iupui> your configure script is unable to find a common
klehigh@iupui> compiler in a common location. Is this a
klehigh@iupui> philosophical decision, or just a function/feature
klehigh@iupui> that hasn't been included yet? Thanks,

It was a philosophical decision that the c compiler on Unix is called
cc and is found in the user's path.

For a variety of reasons, the behavior is different in the upcoming
1.3 release of Kerberos.
We use a more standard autoconf test for the C compiler now.