I've been looking at test failures on macOS for the last several days.
These are the failing tests that I see:
testdbd:
Line 211: failed to fetch sqlite3 driver: DSO load failed
I haven't looked closely at this one yet, but since I didn't point
configure at a recent SQLite3 installation, I suspect it's picking
up the system libraries which are known to be ancient and
incomplete. Could also be related to how the macOS loader searches
for loadable modules at runtime.
testxlate:
Translation from UTF-7 to UTF-8 converts "Edelwei+AN8-" to "Edelweiß-"
This is a bug in the system libiconv that configure finds by
default. Using a newer version of libiconv fixes the conversion bug
and the test.
testsock: most tests fail
sendfile: all tests fail
The server components of the tests fail with:
apr_socket_bind()->48/Address already in use
even though 'netstat' says that port isn't in use. Fixed by changing
the TCP port used by the tests from 8021 to 8022 or 38021. I see
launchd listening on port 8021 on my Mac and it seems that it's this:
https://apple.stackexchange.com/questions/404346/what-is-intu-ec-client-listening-on-tcp-port-8021#404356
I have no idea why someone over at Apple thinks I need an FTP proxy
hogging my ports. Anyway, I propose to change the test ports to 38021,
that should fix the problems on macOS and not cause any new problems on
other platforms. I hope.
-- Brane
