[okl4-developer] okl4 issues

Ashish Bijlani ashish.bijlani at gmail.com
Sat Aug 2 04:11:39 EST 2008


Thanks. This works :)

On Fri, Aug 1, 2008 at 3:49 AM, Frank Kaiser
<frank.kaiser at opensynergy.com> wrote:
> Hi, Ashish
>
> This reminds me at a quoting problem I had a while ago. Try to write
> your command line this way:
>        ./tools/build.py MACHINE=kzm_arm11 PROJECT=iguana
> TEST_LIBS=\"all\"
> The quotes enforce string treatment of the parameter 'all' by Python,
> and the escapes are required to prevent the command line processor from
> removing the quotes.
> Thanks to Geoff for that hint.
>
> Regards
> Frank
>> -----Original Message-----
>> From: developer-bounces at okl4.org [mailto:developer-bounces at okl4.org]
> On Behalf
>> Of Ashish Bijlani
>> Sent: Thursday, July 31, 2008 7:26 PM
>> To: developer at okl4.org
>> Subject: [okl4-developer] okl4 issues
>>
>> 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?
>>
>> 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?
>>
>> -Ashish
>>
>> _______________________________________________
>> Developer mailing list
>> Developer at okl4.org
>> https://lists.okl4.org/mailman/listinfo/developer
>



More information about the Developer mailing list