Issues trying to uplift qmtest for LSB libstdc++ test

[Stew Benedict]

Hi,

I'm working for the Linux Foundation, and we're looking at uplifting the 
qmtest we distribute to 2.4, as 2.2 is getting rather old.  I can 
build/package qmtest fine, but am running into issues now building/running 
the libstdc++ tests.

I'm not really that well versed in using qmtest, so it's quite possible 
I'm overlooking something really obvious.

First issue seems to be the change in _RunTargetExecutable -

build/lib.linux-i686-2.4/qm/test/classes/dejagnu_test.py:
def _RunTargetExecutable(self, context, result, file)

in 2.2 sources:
build/lib.linux-i686-2.4/qm/test/classes/dejagnu_test.py: def 
_RunTargetExecutable(self, context, result, file, dir = None):
 
So I get complaints about too many arguments, as the libstdc++ test has:

qm-classes/qmtest_gcc/v3_test.py: def _RunTargetExecutable(self, context, 
result, file, dir = None):

Tried patching that out to use the 2.4 syntax and then hit:

qm.test.context.ContextException: The context variable 
"CompilerTable.target" was not defined.

Defined 'CompilerTable.target=' in build_binary_testsuite and 
build_v3_dist, and now hit:

exceptions.AttributeError: 'str' object has no attribute 'Run'

Also tried a different approach, keeping the 5 argument 
_RunTargetExecutable, renaming it to _RunLSBTargetExecutable, which 
eventually led me to the same 'str' object has no attribute 'Run'.

Any pointers?
Thanks,
-- 
Stew Benedict
The Linux Foundation