RTEMS for MIPS
Joel Sherrill
joel.sherrill at OARcorp.com
Tue Sep 16 11:03:35 UTC 2003
Ren, Han Tao (Hans) wrote:
>Thomas
>
>Thank you for your message.
>
>Yes, I've installed the BSP to opt/rtems/mips-rtems/.
>
>Let me give more details on what I did.
>Actually, I got different toolchains, one is "sparc-rtems", one is
>"mips-rtems".
>I download the binaries of "sparc-rtems" on http://www.gaisler.com, but I
>had
>to build toolchains for mips-rtems myself, so I download binutils and gcc
>source
>code, as well as the patch files for RTEMS. Then I followed the
>instructions in
>the document "Getting Started with RTEMS for C/C++ Users(4.6.0pre4)" to do
>the building, it passed finally and I got the binaries, but it seemed
>mips-rtems-gcc
>refused to work. However, the sparc-rtems toolchains are working fine.
>The following
>are some log messages.
>
>
Jiri's toolset (TECCS) is setup to take different arguments from the
standard RTEMS toolsets.
If you had used the sparc-rtems tools off of rtems.com, they would have
behaved exactly like
the mips-rtems ones.
>[root at localhost samples]# mips-rtems-gcc -g -O2 hello.c -o hello
>/opt/rtems/lib/gcc-lib/mips-rtems/3.2.2/../../../../mips-rtems/bin/ld:
>warning: cannot find entry symbol _start; defaulting to 0000000000400020
>/tmp/cccZsyHs.o: In function `main':
>/opt/rtems/src/examples/samples/hello.c(.text+0x10): undefined reference to
>`puts'
>collect2: ld returned 1 exit status
>[root at localhost samples]#
>[root at localhost samples]# sparc-rtems-gcc -g -O2 hello.c -o hello
>[root at localhost samples]#
>[root at localhost samples]# mips-rtems-gcc -g -O2 -rtems rtems-hello.c -o
>rtems-hello
>mips-rtems-gcc: unrecognized option `-rtems'
>rtems-hello.c:7:17: bsp.h: No such file or directory
>rtems-hello.c:11: parse error before "Init"
>rtems-hello.c:12: parse error before "ignored"
>rtems-hello.c:31:22: confdefs.h: No such file or directory
>[root at localhost samples]# sparc-rtems-gcc -g -O2 -rtems rtems-hello.c -o
>rtems-hello
>[root at localhost samples]#
>
>I've tried on both Redhat and Solaris platform, the results are same.
>
>Thanks
>
>Hans
>
>
>
>
>
>
>
>
>Hans
>
>-----Original Message-----
>From: Thomas Doerfler [mailto:Thomas.Doerfler at imd-systems.de]
>Sent: Tuesday, September 16, 2003 3:00 PM
>To: Ren, Han Tao (Hans)
>Subject: Re: RTEMS for MIPS
>
>
>Hello,
>
>this is just a guess: Maybe you forgot to "install" the BSP
>you have built. Normally, after configuring and building the
>BSP, it sould be installed with
>
>make install
>
>this will copy the relevant files to a path like
>
>/opt/rtems/mips-rtems/<bsp>/*
>
>Whenever you try to build an application, the compiler
>normally tries to find the include files and libraries in that
>path...
>
>And, naturally, Ralf is right, the command line switch "-
>qrtems" should be visible on the compiler command line. So
>maybe you simply misstyped your command line and the switch "-
>rtems" should in fact be "-qrtems"?
>wkr,
> Thomas.
>
>
>
>
>>Hello
>>
>>I just follow the instructions in the document "Getting Started with RTEMS
>>for C/C++ Users(4.6.0pre4)" to build the toolchains and RTEMS for MIPs.
>>I've successfully built all the toolchains. But when I specified the bsp
>>
>>
>as
>
>
>>"p4600", It failed when building RTEMS. Then I configured the bsp as
>>"jmr3904" and it passed. However, when I built the sample code, it report
>>the following error messages.
>>
>>$ mips-rtems-gcc -g -O2 -rtems rtems-hello.c -o rtems-hello
>>mips-rtems-gcc: unrecognized option `-rtems'
>>rtems-hello.c:7:17: bsp.h: No such file or directory
>>rtems-hello.c:11: parse error before "Init"
>>rtems-hello.c:12: parse error before "ignored"
>>rtems-hello.c:31:22: confdefs.h: No such file or directory
>>
>>Does anybody know where the problem is?
>>
>>Thanks
>>
>>Hans
>>
>>
>
>--------------------------------------------
>IMD Ingenieurbuero fuer Microcomputertechnik
>Thomas Doerfler Herbststrasse 8
>D-82178 Puchheim Germany
>email: Thomas.Doerfler at imd-systems.de
>PGP public key available at: http://www.imd-
>systems.de/pgp_keys.htm
>
>
More information about the users
mailing list