[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120630222129.GA3656@openwall.com>
Date: Sun, 1 Jul 2012 02:21:29 +0400
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Cc: Eric Christopher <echristo@...le.com>
Subject: Re: John the Ripper 1.7.9-jumbo-6
Donovan, Eric -
On Sat, Jun 30, 2012 at 07:46:29PM +0200, newangels newangels wrote:
> I uncomment the first one on the makefile :
>
> # gcc with OpenMP
> OMPFLAGS = -fopenmp
> #OMPFLAGS = -fopenmp -msse2
>
> I run ;
>
> $make macosx-x86-64
>
> I got ;
>
> ********************
> ld: warning: directory not found for option '-L/usr/local/lib'
> ld: warning: directory not found for option '-L/usr/local/ssl/lib'
> ld: warning: option -s is obsolete and being ignored
> Undefined symbols for architecture x86_64:
> "___builtin_object_size", referenced from:
> _BF_std_crypt.omp_fn.0 in BF_std.o
> _crypt_all.omp_fn.0 in cryptsha256_fmt.o
...
> Allways on MacBook Pro : OS : LION 1.7.4
>
> with :
>
> OpenSSL 0.9.8r 8 Feb 2011
> gcc version : 4.2.1
Apparently, you may workaround this by either adding -D_FORTIFY_SOURCE=0
to OMPFLAGS or compiling with gcc rather than with clang/llvm (I think
on recent OS X, its "gcc" is actually clang). One of these changes
should be enough (you shouldn't need to do both).
What's your Xcode version?
Are you able to build 1.7.9-jumbo-5 (not -6) with OpenMP support on
this same system and in this same way (without a workaround) just fine?
If so, that's puzzling.
These may be relevant:
http://comments.gmane.org/gmane.comp.compilers.llvm.devel/37989
http://llvm.org/bugs/show_bug.cgi?id=4380
Eric - I thought you could want to comment on this, such as on whether
this is in fact an instance of the same problem as mentioned at the URLs
above or not and whether it is normal/expected that we're running into
it on OS X 10.7.4 (you fixed the LLVM bug in 2010?)
Thanks,
Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
