Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 31 Aug 2011 17:38:49 -0400
From: "Robert Harris" <rs904c@...scape.net>
To: <john-dev@...ts.openwall.com>
Subject: RE: Build Issue on Solaris, John v1.7.8 jumbo-5 August 24, 2011

Magnum,

I hope this clears up what I was saying.

When I delete the line below, from the JtR v1.7.8 with jumbo-2 or jumbo-5
stdint.h file, I get a successful build of solaris-x86-64-gcc.  

typedef unsigned long long uint64_t;


I suspect other Solaris builds would be affected the same way.

-Robert B. Harris from VA

-----Original Message-----
From: magnum [mailto:rawsmooth@...dband.net] 
Sent: Wednesday, August 31, 2011 4:49 PM
To: john-dev@...ts.openwall.com
Subject: Re: [john-dev] Build Issue on Solaris, John v1.7.8 jumbo-5 August
24, 2011

On 2011-08-25 23:25, Robert Harris wrote:
> As you can see, Solaris 64-bit (perhaps Solaris 32-bit) actually defines
> uint64_t in int_types.h    So, only that conflicts with the JtR
definitions.
>
> ****So, the only solution that works for me through trial and error, is to
> deleted the following line out of stdint.h:
> typedef unsigned long long uint64_t;
>
> **** With this line deleted, my build of solaris-x86-64-gcc,
> works.**********
>
> What issues are there with deleting this? Other comments about this?

It is unclear to me if you mean "can I delete this line in order to 
build JtR on this machine?" or "should we delete this line in the Jumbo 
tree?". I initially read it as the former and I take it Solar read it as 
the latter.

By all means, if deleting that line makes it build without problems, 
then you are home free as far as I can imagine.

magnum

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ