This would be due to a new feature to detect import conflicts.
If a library imports 2 libraries exporting the same symbol, an error
is now generated at compile time. This feature is key in large systems
where you often have tens of imports per library. Also, what this new
feature means is that import order is now proven to be non-important
another very important feature for complex systems.
All this said, this change popped many conflicts that where resolved
on Windows but unfortunately, I don't have access to an OS X box and
Stéphane is on vacation at the moment :(
Still. I took a blind shoot at it. Can you let me know if it fixed the problem?
Thanks,
Guillaume