Is there any framebuffer testcases?

[Chris Johns]

On 7/04/2016 11:20 PM, Peng Fan wrote:
> Sorry. Missed to attach error info when compile tiff
>
> Please kindly give comments on this.
>

 From the log ...

/home/Freenix/development/rtems/4.12/lib/gcc/arm-rtems4.12/6.0.0/../../../../arm-rtems4.12/bin/ld: 
warning: cannot find entry symbol _start; defaulting to 0000000000008000
/home/Freenix/development/rtems/4.12/lib/gcc/arm-rtems4.12/6.0.0/../../../../arm-rtems4.12/lib/libc.a(lib_a-fclose.o): 
In function `_fclose_r':
/home/Freenix/work/forfun/rtems/rtems-source-builder/rtems/build/arm-rtems4.12-gcc-6-20160124-newlib-2.3.0.20160104-x86_64-linux-gnu-1/build/arm-rtems4.12/newlib/libc/stdio/../../../../../gcc-6-20160124/newlib/libc/stdio/fclose.c:117: 
undefined reference to `_Mutex_recursive_Release'

This looks like a regression with RTEMS related to the addition of 
_Mutex_recursive_Release and friends.

RTEMS should link an executable without error because we need this 
working so configure link tests do not fail when they should not. In 
this case it is the an application 'mkg3states' that is being linked and 
this use to work

I think these symbols are related to changes in gcc and/or newlib.


I seem to remember a dummy.c file or something like that which had some 
symbols we needed so the link not fail like this.

I hope someone who knows what happens here can offer some advice.

Chris