[okl4-developer] okl4 issues
Geoffrey Lee
glee at ok-labs.com
Fri Aug 1 10:39:57 EST 2008
On Thu, Jul 31, 2008 at 12:26:24PM -0500, Ashish Bijlani wrote:
> Hi,
>
> Command "./tools/build.py MACHINE=kzm_arm11 PROJECT=iguana
> TEST_LIBS=all" gives errors -
>
> scons: Reading SConscript files ...
> architecture arm is not yet supported by libcompat.
> architecture arm is not yet supported by libcompat.
> /okl4/okl4-2.1.1/tools/build.py:2959 Error: local variable 'x'
> referenced before assignment
>
> I think changing 'x' to 'arg' in "/tools/build.py" at line "2959" will
> fix this. However, still "test_libs=all" doesn't work. Any ideas?
I got a fresh copy of the 2.1.1 patch 9 release as well as 2.1 and I tried
to run the command above and got a working binary. It would appear
you have made some modifications to OKL4 which would cause this
problem?
>
> scons: Reading SConscript files ...
> architecture arm is not yet supported by libcompat.
> architecture arm is not yet supported by libcompat.
> /home/ashish/okl4/okl4-2.1.1/tools/build.py:2959 <built-in function
> all> is not a valid argument for option TEST_LIBS. Valid options are:
> ['hash', 'mutex', 'iguana', 'circular_buffer', 'queue', 'fs', 'll',
> 'range_fl', 'bit_fl', 'bootinfo', 'c', 'binary_tree', 'atomic_ops',
> None, 'all', None, 'posix']
> make: *** [build/images/image.elf] Error 2
> The recent okl4-2.1.1 seem to be reporting L4_lock() based mutex test
> in "l4test" suite cases as failures, whereas the previous version
> "okl4-2.1.0" doesn't report them as failures. I guess one of the
> versions has a problem or probably I'm missing something?
>
One should use l4test with mutex_type=user.
> -Ashish
-gl
>
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer
>
--
More information about the Developer
mailing list