[GSOC] How to compile with sparc-rtems4.11-g++ command?

[Xiaochen Pan]

Yes, you are right. I have made some change to the Makefile and I forgot about it. Thank you. I am so ashamed.

I changed it back, the error message does not appear again. But it still have not produce the executable file, the message is as follows:

make: *** No rule to make target 'o-optimizeo-optimize/runner.exe', needed by 'all'. Stop.

regards,
xiaochen
On Jun 21, 2012, at 5:48 PM, Joel Sherrill wrote:

> 
> 
> I suspect a bug in your makefile where $(ARCH) is not before $(OBJS).
> 
> Notice in this fragement all depends on $(ARCH) and $(PGM).
> $(PGM) depends on $(OBJS). $(ARCH) will be "built" before $(PGM)'s
> dependencies are addressed.
> 
> all:    ${ARCH} $(PGM)
> 
> $(PGM): $(OBJS)
>        $(make-exe)
> 
> If that isn't it, send me a tarball and I will look at it.
> 
> --joel
> 
> On 06/21/2012 04:30 PM, panx at seas.upenn.edu wrote:
>> Sorry, I also modified it to be
>> CXXSRCS = runner.cpp
>> CXXOBJS = $(CSRCS:%.cpp=${ARCH}/%.o)
>> 
>> Quoting panx at seas.upenn.edu:
>> 
>>> Here is another one error message:
>>> 
>>> sparc-rtems4.11-g++
>>> -B/home/rtems/rtems-4.11-work/b-sis/sparc-rtems4.11/sis/lib/ -specs
>>> bsp_specs -qrtems   -g -Wall  -g    -mcpu=cypress     -c   -o
>>> o-optimize/runner.o runner.cc
>>> Assembler messages:
>>> Fatal error: can't create o-optimize/runner.o: No such file or directory
>>> make: *** [o-optimize/runner.o] Error 1
>>> 
>>> In the makefile from example-v2, I modified the following part:
>>> CSRCS = test.c
>>> COBJS = $(CSRCS:%.c=${ARCH}/%.o)
>>> to be like this:
>>> CSRCS = runner.cpp
>>> COBJS = $(CSRCS:%.cpp=${ARCH}/%.o)
>>> 
>>> Which part I was not doing correctly?
>>> 
>>> Regards,
>>> xiaochen
>>> 
>>> Quoting Joel Sherrill<joel.sherrill at OARcorp.com>:
>>> 
>>>> On 06/21/2012 03:54 PM, Xiaochen Pan wrote:
>>>>> Hello all,
>>>>> 
>>>>> Here is the command:
>>>>> 
>>>>> sparc-rtems4.11-g++ -o runner runner.cpp
>>>>> 
>>>> You are still not building with the arguments to have RTEMS and the
>>>> BSP .h files available or included with your application.
>>>> 
>>>> If you use the Makefiles from examples-v2, simply list your C++
>>>> sources as CXXSRCS like this
>>>> 
>>>> CXXSRCS = init.cc
>>>> 
>>>>> Here are the error messages:
>>>>> *
>>>>> *
>>>>> */opt/rtems-4.11/lib/gcc/sparc-rtems4.11/4.6.2/../../../../sparc-rtems4.11/bin/ld: warning: cannot find entry symbol _start; defaulting to
>>>>> 00010074
>>>>> /opt/rtems-4.11/lib/gcc/sparc-rtems4.11/4.6.2/libstdc++.a(eh_alloc.o): In
>>>>> function `__gthread_mutex_destroy':
>>>>> /builddir/build/BUILD/rtems-4.11-sparc-rtems4.11-gcc-4.6.2/build/sparc-rtems4.11/libstdc++-v3/include/sparc-rtems4.11/bits/gthr-default.h:114: undefined reference to
>>>>> `rtems_gxx_mutex_destroy'
>>>>> /opt/rtems-4.11/lib/gcc/sparc-rtems4.11/4.6.2/libstdc++.a(locale.o): In
>>>>> function `__gthread_mutex_destroy':
>>>>> /builddir/build/BUILD/rtems-4.11-sparc-rtems4.11-gcc-4.6.2/build/sparc-rtems4.11/libstdc++-v3/include/sparc-rtems4.11/bits/gthr-default.h:114: undefined reference to
>>>>> `rtems_gxx_mutex_destroy'
>>>>> /opt/rtems-4.11/lib/gcc/sparc-rtems4.11/4.6.2/libstdc++.a(locale_init.o):
>>>>> In function `__gthread_mutex_destroy':
>>>>> /builddir/build/BUILD/rtems-4.11-sparc-rtems4.11-gcc-4.6.2/build/sparc-rtems4.11/libstdc++-v3/include/sparc-rtems4.11/bits/gthr-default.h:114: undefined reference to
>>>>> `rtems_gxx_mutex_destroy'
>>>>> collect2: ld returned 1 exit status*
>>>>> *
>>>>> *
>>>>> How to fix this problem?
>>>>> 
>>>>> regards,
>>>>> xiaochen
>>>>> 
>>>> 
>>>> -- 
>>>> 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
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>> 
> 
> 
> -- 
> 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
> 
>