-no-undefined problem with new libtool
Submitted by Behdad Esfahbod
Link to original bug (#345511)
Description
Sometime ago I switched to using -no-undefined on non-Win32 systems too. That helps catch misspellings at compile time...
Now with libtool from CVS, libtool decides to not make shared libraries because of the -no-undefined.
I'm going to report it to libtool maintainers. This bug is just here to remind me to remove the -no-undefined if that's not fixed upstream.