[23859] in Kerberos
RE: building kerberos on 64 bit processor
daemon@ATHENA.MIT.EDU (Heilke, Rainer)
Mon May 9 18:20:52 2005
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Date: Mon, 9 May 2005 15:27:22 -0600
Message-ID: <A28A519A6A08AD4A9553A9DB5265FD3E0353FD80@is030.atco.com>
From: "Heilke, Rainer" <Rainer.Heilke@atcoitek.com>
To: <kerberos@mit.edu>
Content-Transfer-Encoding: 8bit
Errors-To: kerberos-bounces@mit.edu
Or you can do it this way. :-) We've just found it generally easier
(and more reliable/definitive when building) to make sure it's a fully
64bit gcc.
Rainer
> -----Original Message-----
> From: kerberos-bounces@mit.edu
> [mailto:kerberos-bounces@mit.edu] On Behalf Of Ken Raeburn
> Sent: Monday, May 09, 2005 3:22 PM
> To: 'kerberos@mit.edu'
> Subject: Re: building kerberos on 64 bit processor
>
>
> On May 9, 2005, at 16:55, Heilke, Rainer wrote:
> > Since you're on Linux, I would add that gcc will need to be built as
> > 64bit. Otherwise, it may still build Kerberos as 32bit,
> because it's
> > all
> > (your version of) gcc knows.
>
> If it is a system that has a 32-bit mode and the compiler defaults to
> 32-bit mode (the original poster didn't say *what* kind of 64-bit
> system it is), then at least for some architectures it should be
> sufficient to give gcc the right option(s) to generate 64-bit code.
> There does seem to be a bug in our current release where the CFLAGS
> value specified at configure time isn't always passed to all
> invocations of the compiler, so I'd recommend passing the option via
> CC, kind of like this command that should build a 64-bit build on
> Solaris:
>
> $ ./configure --prefix=... CC='gcc -m64'
>
> Ken
>
> ________________________________________________
> Kerberos mailing list Kerberos@mit.edu
> https://mailman.mit.edu/mailman/listinfo/kerberos
>
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
