[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <001801cb6731$d56ba090$8042e1b0$@net>
Date: Fri, 8 Oct 2010 17:42:58 -0400
From: "Robert Harris" <rs904c@...scape.net>
To: <john-users@...ts.openwall.com>
Subject: RE: Patch for Makefile, concerning Solaris x86
Alex,
I was thinking about doing it in the global LDFLAGS, but that would affect
all builds. Wouldn't that cause a problem? (I haven't checked yet, if it
would).
-----Original Message-----
From: Solar Designer [mailto:solar@...nwall.com]
Sent: Friday, October 08, 2010 4:32 PM
To: john-users@...ts.openwall.com
Subject: Re: [john-users] Patch for Makefile, concerning Solaris x86
Robert,
On Wed, Oct 06, 2010 at 12:34:14AM -0400, Robert Harris wrote:
> I'm making a patch that adds "-lnsl -lsocket" to the LDFLAGS of
> "solaris-x86-64-gcc","solaris-x86-sse2-gcc", "solaris-x86-mmx-gcc", and
> "solaris-x86-any-gcc" in the Makefile.
>
> I'm wondering if any other of the Solaris areas need this flag as well?
All solaris-* targets need it (this means solaris-sparc* and *-cc ones
as well), albeit only for the tgtsnarf program in the jumbo patch. It
is easier to add the options to the global LDFLAGS rather than to try
to do it for tgtsnarf only. In fact, the jumbo patch is already dirty
in this aspect anyway - it similarly unnecessarily links some programs
against OpenSSL. So we can continue this "tradition" for now...
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.
