I wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> Looks like there are still problems on Windows/mingw and OpenBSD - see
>> frogmouth and curculio on the buildfarm.
> Yeah. I just sent you an offlist request to look into what's happening
> on frogmouth, and I'm talking to curculio's owner as well.
The answer on curculio seems to be that OpenBSD doesn't bother with
providing symlinks like libpython2.7.so -> libpython2.7.so.0.0.
They've evidently hacked the linker so that it will find such a shlib
even when told only "-lpython2.7". I can't say that I think that's
a good design --- what if there's more than one version installed? ---
but there you have it. (Thanks to Mikael Kjellstrom for assisting
with this investigation.)
This seems reasonably easy to fix by allowing the configure probe
to accept files that have the expected name plus some trailing junk.
I can't tell what to make of frogmouth's results from here. Awaiting
your input. If you're not sure what to check, it would be helpful
to see the results of
python -c "import distutils.sysconfig; print(distutils.sysconfig.get_config_vars())"
and to know exactly where libpython.dll is and what it's named.
regards, tom lane