[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: -no-undefined on Win32
From: |
Bob Friesenhahn |
Subject: |
Re: -no-undefined on Win32 |
Date: |
Mon, 28 Apr 2014 20:58:56 -0500 (CDT) |
User-agent: |
Alpine 2.01 (GSO 1266 2009-07-14) |
On Mon, 28 Apr 2014, Evgeny Grin wrote:
Good. But requiring "-no-undefined" for Win32 flag lower probability of
successful compile.
In what way does it lower the probability of a successful compile?
Static linkage is much more portable than dynamic.
The situation you outlined is due to a defective package
preparation/build environment. A proper build has just one version of
a given library in a link.
Regardless, it is very unlikely that libtool will react to your plea
(if it does at all) in a timely fashion and so you are best advised to
fix your build without relying on significant changes in libtool.
Bob
--
Bob Friesenhahn
address@hidden, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
- -no-undefined on Win32, Evgeny Grin, 2014/04/17
- Re: -no-undefined on Win32, Bob Friesenhahn, 2014/04/18
- Re: -no-undefined on Win32, Evgeny Grin, 2014/04/18
- Re: -no-undefined on Win32, Bob Friesenhahn, 2014/04/19
- Re: -no-undefined on Win32, Evgeny Grin, 2014/04/28
- Re: -no-undefined on Win32,
Bob Friesenhahn <=
- Re: -no-undefined on Win32, Evgeny Grin, 2014/04/29
- Re: -no-undefined on Win32, Peter Rosin, 2014/04/29
- Re: -no-undefined on Win32, Evgeny Grin, 2014/04/29
- Re: -no-undefined on Win32, Peter Rosin, 2014/04/29