test infrastructure ideas appreciated ...

[Michael Stahl]

On 04.06.2015 18:32, Michael Meeks wrote:
> Hi Robert,
> 
> On Wed, 2015-06-03 at 15:44 +0200, Robert Antoni Buj i Gelonch wrote:
>> We could add an automatic validation test for checking the discovery
>> of dynamic library dependencies on OS X & Linux.
>>       * OS X: otool -L file
>>       * Linux: ldd file
> 
> 	Sounds interesting - the concern would be having added new
> dependencies ? or what could we check with that ?

that's actually a good idea, as the recent bibisect Linux 5.0 accident
has demonstrated, see also commit
f4844a9abebcb0451161625c42a1e2b48796102d

we could have a test that runs something like readelf -d | grep
"(NEEDED)", filter out our own libraries, and then filters against a
whilelist of known-good system libraries; anything outside the whitelist
shouldn't be required.

it might even be useful on Mac OS X: while you do have a proper SDK
there and not a random collection of -devel packages, it might still be
possible that some bundled library's crazy configure script finds some
random stuff installed via Fink/MacPorts/etc., which would cause the
same issues.