gcc-4.3.3-haiku-090129 forbids undefined symbols in shared libraries
|Reported by:||titer||Owned by:||mmlr|
gcc4 currently adds -no-undefined unconditionally when linking, which I know is expected behavior (mmlr mentioned it in his blog post announcing the native gcc4).
This is going to cause build issues with a number of projects though, which assume the usual behavior of allowing undefined symbols in shared libraries (e.g. try building libevent), and unfortunately I don't believe we can convince everybody else to stop using this "feature".
Updating the specs to only enable -no-undefined when linking apps fixes it (same way gcc2 does it).