Hi, That's mainly because the RSB is fetching an upstream gcc-4.8.3 version and it applies my old patch there. I suggested to temporarily use the current or1k up-to-date repos from github (like Epiphany tools), which incorporate our RTEMS stuff, and are synced with gcc-5x version. FWIW Christian told me two weeks ago that they managed to contact the last code contributor to finish the FSF paper work, and hopefully the or1k-gcc will be upstream soon.
On Wed, Oct 21, 2015 at 7:42 PM, Joel Sherrill <joel.sherr...@oarcorp.com> wrote: > Hi > > I think the or1k tools are out of sync with RTEMS now. > > or1k-rtems4.11-gcc -B../../../../../generic_or1k/lib/ -specs bsp_specs > -qrtems -O2 -O0 -g -Wall -Wmissing-prototypes > -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs -O2 > -o hello.exe init.o > /data/home/joel/rtems-4.11-work/tools/bin/../lib/gcc/or1k-rtems4.11/4.8.3/../../../../or1k-rtems4.11/lib/libc.a(lib_a-puts.o): > In function `_puts_r': > /data/home/joel/rtems-4.11-work/rtems-source-builder/rtems/build/or1k-rtems4.11-gcc-4.8.3-newlib-f296bb3569839b0217ec1a775165d239877e3548-x86_64-linux-gnu-1/build/or1k-rtems4.11/newlib/libc/stdio/../../../../../gcc-4.8.3/newlib/libc/stdio/puts.c:102: > undefined reference to `_Mutex_recursive_Release' > ..... > > Any suggestions? > > --joel -- Hesham _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel