Hi all,
Having spent a few hours tussling with the load-order bogey, I found what I
think is a bit of a gap in the win32 build process.
There are no configure warnings at all when there's a missing extension
dependency... only a bailout if you try to build a dependency as shared for
a static extension. The need to bail out would depend on how full-on the
'dependency' in question is, and I'd guess that can be variable.
Trivial patch attached, would've saved me a lot of brain-ache if it had been
in CVS yesterday but see what you think.
- Steph
