[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110714094447.GD27991@openwall.com>
Date: Thu, 14 Jul 2011 13:44:47 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: Any flags needed to statically link openmp in Linux
Robert, magnum -
On 2011-07-11 19:11, Robert B. Harris wrote:
>I'm working on compiling JtR omp versions for Linux.
>I am wondering if there are any LDFLAGS to statically link omp?
IIRC, simple -static worked for me. I have 1.7.6-omp-des-4 and
1.7.6-omp-des-7 static binaries that I built on Owl with gcc 4.5.0 a
year ago, and I tested these on a variety of systems (other Owl systems,
CentOS 5, maybe others) - all worked fine.
On Tue, Jul 12, 2011 at 03:29:36AM +0200, magnum wrote:
> Some info here:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39176#c7
>
> Excerpt from that page:
> >This has been repeated many times. Don't use -static for threaded
> >programs, it
> >is really bad idea, and if you really have to, you need to link the whole
> >libpthread.a in (-Wl,--whole-archive -lpthread -Wl,--no-whole-archive),
> >otherwise if it works, it is by pure luck.
It seems I was lucky.
> Some interesting reading here too:
> http://www.akkadia.org/drepper/no_static_linking.html
>
> Excerpt from that page:
> >Conclusion: Never use static linking!
>
> ;-)
Sure. ;-)
Some of the reasons given there are why for the GUI we'll likely have to
use hybrid linking - static for some libs (Qt?), dynamic for others
(glibc?) JtR Pro for Linux is linked against a purposefully old version
of glibc dynamically (so it works with newer versions as well due to
symbol versioning, but does not strictly require those newer versions),
but with OpenSSL statically.
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.
