RE: My dynamic loader refuses to load libQt5Core because of the ABI tag note

["Krzysztof Żelechowski" <krzysztof.zelechowski@prospeo.com.pl>]

I repeat the most important stuff:

/usr/lib/YaST2/bin/y2controlcenter

	/usr/lib/YaST2/bin/y2controlcenter: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory

LD_DEBUG=all returns a ton of stuff but there is no mention of an OS version mismatch, just that the library could not be found, which is mind-boggling.

readelf -n /usr/lib64/libQt5Core.so.5

	Displaying notes found in: .note.ABI-tag
	Owner                Data size        Description
	GNU                  0x00000010       NT_GNU_ABI_TAG (ABI version tag)
	OS: Linux, ABI: 3.17.0

objcopy -R .note.ABI-tag /usr/lib64/libQt5Core.so.5 /tmp/libQt5Core.so.5

LD_LIBRARY_PATH=/tmp /usr/lib/YaST2/bin/y2controlcenter

	qt.qpa.xcb: could not connect to display

cat /proc/sys/kernel/osrelease

	4.4.0-19041-Microsoft

This shows that
	1) the library is present and correct, 
	2) the dynamic loader does not care about diagnostics, 
	3) the dynamic loader is undocumented as to how it uses the ABI tag note and where it takes its idea of OS version from.

How do I examine kernel vDSO?

I have no way of reporting this problem to the distro until we have confirmed it is the ABI note problem as I suppose it is, and I expect it to be confirmed by an appropriate diagnostic emitted by the dynamic loader.  I would rather not tell the distro maintainers to dig into function open_verify to see that, especially as you need to know that it compares %EAX to %EDX and you have to si and figure out which register represents which version.

Thanks for your help,
Chris