[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091029044458.GA27054@openwall.com>
Date: Thu, 29 Oct 2009 07:44:58 +0300
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: My patches (Performance, options, mingw, vc, generic md5, phpass, etc)
On Wed, Oct 28, 2009 at 11:19:59PM -0500, JFoug wrote:
> Might it be better to make a new rule, and leave that one. Then
> you could have a macosx32-x86-sse2 or something like that, since
> that is what you are specifying as the build, with the -m32's
I am hoping that there's no need for that, and I don't want to add a new
target unnecessarily. "-m32" should be harmless on older OS X, but I am
asking Erik in case he knows something special about that.
There are two similar targets right now, which are "undocumented":
# @echo "linux-x86-64-32-sse2 Linux, x86-64, 32-bit with SSE2"
# @echo "linux-x86-64-32-mmx Linux, x86-64, 32-bit with MMX"
I've just verified that these work on 32-bit x86 as well, but probably
not on ancient versions of Linux (with ancient gcc and binutils), which
is why I kept these as separate targets. OS X was introduced relatively
recently, so I hope that all versions of it understood "-m32".
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.
