>> If disabled, it will compile correctly in Darwin. Should we put it as a
>> condition only for compiling in Windows environment?
>
> Seems to be a good solution.
>
Just prepared a patch for this, which will prevent using --no-undefined
except for mingw32 compilation (so Mac OS X compilation should not use
it). Not sure if this is the best way to handle this, anyway.
I think that it is a good solution for now. Later we can investigate
the reason for Macos10 to crash when using --no-undefined.
Please commit it and ack.
Commited.
