or1ksim fails to build

Hesham Moustafa heshamelmatary at gmail.com
Fri Aug 29 20:04:35 UTC 2014


On Fri, Aug 29, 2014 at 9:24 PM, Hesham Moustafa
<heshamelmatary at gmail.com> wrote:
> On Fri, Aug 29, 2014 at 9:19 PM, Joel Sherrill
> <joel.sherrill at oarcorp.com> wrote:
>> Hi
>>
>> I think something isn't quite right.  I don't know if gcc isn't including
>> these or the bsp_specs isn't picking them up. It is a long holiday weekend
>> and I just wanted to throw this out since I don't have time to investigate.
>>
>> or1k-rtems4.11-gcc -B../../../../../or1ksim/lib/ -specs bsp_specs
>> -qrtems -O2 -O0 -g -Wall -Wmissing-prototypes
>> -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs
>> -O2   -o nsecs.exe init.o empty.o
>> ../../../../../or1ksim/lib/librtemscpu.a(libscore_a-threadhandler.o): In
>> function `_Thread_Handler':
>> /users/joel/rtems-4.11-work/rtems-testing/rtems/build-or1k-or1ksim-rtems/or1k-rtems4.11/c/or1ksim/cpukit/score/../../../../../../rtems/c/src/../../cpukit/score/src/threadhandler.c:181:
>> undefined reference to `_init'
>> ../../../../../or1ksim/lib/librtemscpu.a(libcsupport_a-newlibc_exit.o):
>> In function `_exit':
>> /users/joel/rtems-4.11-work/rtems-testing/rtems/build-or1k-or1ksim-rtems/or1k-rtems4.11/c/or1ksim/cpukit/libcsupport/../../../../../../rtems/c/src/../../cpukit/libcsupport/src/newlibc_exit.c:43:
>> undefined reference to `_fini'
>> collect2: error: ld returned 1 exit status
>>
> What's the configure line you used to build? I used to --disable-posix
> and --disable-itron to avoid some of building errors.
Well, I removed these --disable-itron and --disable-posix, and it
builds as before (except for the missing _CPU_Context_validate and
other one). I will have to build the entire tool-chain from RSB again,
and see if I got the same error.
>> --
>> Joel Sherrill, Ph.D.             Director of Research & Development
>> joel.sherrill at OARcorp.com        On-Line Applications Research
>> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>> Support Available                (256) 722-9985
>>



More information about the devel mailing list