[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABeUhws4A=3LUz+DSt0CZFU8DjAWgH04SmpPXQnYwU-kx937TA@mail.gmail.com>
Date: Sun, 1 Jul 2012 01:47:21 +0200
From: newangels newangels <contact.newangels@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: John the Ripper 1.7.9-jumbo-6
Alexander,
Thanks for reply, here my answer's ;
2012/7/1, Solar Designer <solar@...nwall.com>:
> 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?
XCODE 4.3.1 for LION
& Command-Line-Tools ( jun 2012 version)
https://developer.apple.com/library/ios/#documentation/DeveloperTools/Conceptual/WhatsNewXcode/00-Introduction/Introduction.html
https://developer.apple.com/xcode/
Xcode change, command-line-tools is an separated pakg now
=https://developer.apple.com/library/ios/#documentation/DeveloperTools/Conceptual/WhatsNewXcode/Articles/xcode_4_3.html
Concern GGC, yes once i run "Make xxxxx" i see he use $gcc -x.....
Concern "-D_FORTIFY_SOURCE=0", i don't understand well where i have to
add this line, can you please tell me if it's an line addition or on
the right of the actual one's ?
> 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
I just download an 1.7.9-5 & the same error !
Without touching the MakeFile for enabling OpenMP support, that's work
perfectly !
Thanks for the links, ok i read them....
What i do not undertand is how Erik Winkler success his 1.7.9-5, we
are both on LION !
Is the build i use actualy ( Erik W. one)
Anyway, i hope we can resolve this issue, thanks agin for your time.
Donovan
> 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.
