Setup: an old Fedora 27 Linux, x86_64, wayland-client 1.14

$ rpm -qa | grep wayl | sort
egl-wayland-1.0.3-2.20180201git6f5f7d0.fc27.x86_64
egl-wayland-devel-1.0.3-2.20180201git6f5f7d0.fc27.x86_64
gnome-session-wayland-session-3.26.1-1.fc27.x86_64
ibus-wayland-1.5.17-6.fc27.x86_64
libwayland-client-1.14.0-2.fc27.x86_64
libwayland-cursor-1.14.0-2.fc27.x86_64
libwayland-server-1.14.0-2.fc27.x86_64
mesa-libwayland-egl-17.3.9-1.fc27.x86_64
mesa-libwayland-egl-devel-17.3.9-1.fc27.x86_64
qt5-qtwayland-5.9.6-1.fc27.x86_64
wayland-devel-1.14.0-2.fc27.x86_64
wayland-protocols-devel-1.10-1.fc27.noarch
xorg-x11-server-Xwayland-1.19.6-7.fc27.x86_64

As of 2.0.16, where lots of wayland improvements went in, I get no
windows at all, e.g. with testsprite2 program: Hitting Ctrl-C quits
the test program. With 2.0.14 and older (tested down to v2.0.7), I
properly get a window (although w/o decorations, as expected.) This
is somewhat a problem, because with SDL2 builds from latest sources,
I have to set SDL_VIDEODRIVER=x11 to run programs properly
because wayland now has priority over x11.

Any hints for solving this? (Assuming it is actually solvable..)
Are the wayland library requirements changed somehow but autotools
is unaware of it? (no issues building, though..)