-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 11.02.2016 11:03, Peter Rosin wrote: > Well said, I would also like to add that libtool -no-undefined *does* *not* > imply ld --no-undefined. I.e. If you add libtool -no-undefined, then the > *only* thing that changes is that libtool actually attempts the shared > build. Libtool must attempt to build shared version if configured with "--enable-shared" and must not attempt to build it if configured with "--disable-shared". It's up to linker to fail if shared build is not possible. "Configure" job is to resolve everything that required. On W32 this sounds like "-linker-will-not-fail". Why make any predictions or assumptions if it possible to just try to link? > Conditionally adding -no-undefined for systems where it matters is overly > defensive. Not agree. Let's consider that some dev is working on porting some lib to W32 (or AIX). Lib is already ported to Linux/Darwin/FreeBSD/OpenBSD/NetBSD/Solaris/HP-UX. And usually some ports contain OS-specific code parts. This developer need to add "-no-undefined" flag for new port. There are two choices: add flag unconditionally and test lib under all OSes (better - with all possible options and on different OS versions) or just conditionally add flag for specific OS. I bet which way will be chosen. Repeat once more: with OS-specific code parts you can't add "-no-undefined" unconditionally. - -- Best Wishes, Evgeny Grin -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWvG9HAAoJEL96xKXqwrr0awwH/3HLwxmFdtCm9OuiJbq2hicS 7OalbEbCAuB3hYiey9zNXAHeGw00/vioNjWIfkb/urMbybXVQ1u1ZyGsvrj5fw+O 5G0wbhdYAg+ZSShy+Glzzp2701FZBIlS7OkKIKI8CCP20UyJ0NRO9NHWEFkFl+0M 86Gc8QbTr5v+8CuSQCog3BPK5k96QujJHBbwBbcmwaZQFODlL7VnfP3XGPb3AJYl 5tU63xyYOEj3ODrlF4cu3s6I2fdQY9SYnzOREJ9irsqODoztWWOMjdlQW/sVml3Q QjnPvaBqhfjFsh0m9BeMSsPs/KXk3LmeZlH5TlNmcsrjgRuylsfxX+bAqSWv+jM= =oF06 -----END PGP SIGNATURE----- _______________________________________________ https://lists.gnu.org/mailman/listinfo/libtool