Kerberos MIT on Solaris
shuque at isc.upenn.edu
Thu Aug 19 11:46:24 EDT 2010
Note: I haven't tested this myself, but something like
the following will probably work:
env CC=cc CFLAGS='-xarch=generic64' ./configure ..
If the right cc isn't in your path, you might have to change
"CC=cc" to "CC=/opt/SUNWspro/bin/cc".
If you're linking with 64-bit libraries in /usr/sfw/lib (eg.
Sun's bundled openssl), you might also need to add:
On Thu, Aug 19, 2010 at 08:09:05AM -0700, vir vir wrote:
> Hi Ken,
> Thank you for your response.
> If I want to compile using Sun compiler and not gcc . How I can set the Sun compiler to the ./configure file?
> --- On Thu, 8/12/10, Ken Raeburn <raeburn at MIT.EDU> wrote:
> From: Ken Raeburn <raeburn at MIT.EDU>
> Subject: Re: Kerberos MIT on Solaris
> To: "vir vir" <vitrou2004 at yahoo.com>
> Cc: krbdev at mit.edu
> Received: Thursday, August 12, 2010, 7:57 AM
> On Aug 12, 2010, at 10:15, vir vir wrote:
> > Hi,
> > I found all the files and the paths.
> > All the libraries were created. The libraries are 32 bit what should I change in the configure file or somewhere else to create 64 bit
> It's normally created using the defaults for whichever compiler you're using, so if you would normally build 32-bit code, that's what it does. (Though it does choose gcc over the native compiler, if you've got both and you don't tell it otherwise.) So, it depends in part on what compiler you're using. You could try something like:
> ./configure CC='gcc -m64'
> in a freshly unpacked source tree (i.e., with no object files, saved configuration data, etc). The CC= spec will override the default compiler selection mechanism.
> krbdev mailing list krbdev at mit.edu
University of Pennsylvania.
More information about the krbdev