Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 17 May 2013 13:33:06 +0000 (GMT)
From: Kyle Gray <nox@....com>
To: john-users@...ts.openwall.com
Subject: Re: Make issues with make clean macosx-x86-64-native

Magnum, thanks for the quick response.

When I run "which as" I get the correct path "/usr/local/bin/as"

Got any other ideas what might be going on?

On May 17, 2013, at 07:36 AM, magnum <john.magnum@...hmail.com> wrote:

On 17 May, 2013, at 0:52 , Kyle Gray <nox@....com> wrote:
> I just downloaded the latest bleeding jumbo and I'm getting an error when attempting to make clean macosx-x86-64-native.
> 
> I've followed the instructions:
> 
> 1. Install Homebrew
> 2. Install Homebrew's openssl and gcc
> 3. From your base "john" directory:
> cp -avi src/osx_as_wrapper.sh /usr/local/bin/as
> 4. Link whatever gcc version you got from Homebrew to just "gcc" in the
> /usr/local/bin directory. This example is for gcc-4.7:
> ln -s gcc-4.7 /usr/local/bin/gcc
> 5. Make sure /usr/local/bin preceeds /usr/bin in your $PATH
> 
> And all seems good.
> 
> When I run make clean macosx-x86-64-native, I get the following errors:
> 
> gcc -c -Wall -Wdeclaration-after-statement -O2 -fomit-frame-pointer -I/usr/local/include -DHAVE_GMP -DHAVE_KRB5 -DHAVE_CRYPT -march=native -Wno-deprecated-declarations -funroll-loops gladman_pwd2key.c
> /var/folders/n8/phvcf3kn2_356yp_fn9280qw0000gn/T//ccLd9HBH.s:40:2: error: invalid instruction mnemonic 'vcvttsd2siq'
> vcvttsd2siq %xmm3, %rsi
> ^~~~~~~~~~~
> make[1]: *** [gladman_pwd2key.o] Error 1
> make: *** [macosx-x86-64-native] Error 2

This indicates that you did not get the as wrapper before the native as in PATH. What does "which as" output? It should say "/usr/local/bin/as" and the latter should be the script you copied in #3.

magnum

Content of type "text/html" skipped

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.