This is the mail archive of the crossgcc@cygnus.com mailing list for the crossgcc project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
On Fri, 24 Jul 1998, Juan Zamorano Flores wrote: > First, I installed cross-binutils and cross-gcc. After, I cross-compiled > newlib and RTEMS-3.6.0. 3.6.0 has some bugs in the POSIX stuff but threads basically worked then. > As RTEMS is a POSIX Run-Time System and it is the RTS for GNAT/SPARC > I cross-compiled GNAT to my mc68020 embedded target without errors but I > have not concurrency neither timing. I don't know if I have a RTEMS > configuration problem or the problem is in GNAT/RTEMS interface. GNAT/RTEMS also works on the PowerPC and i386. > > Also, gcc-2.7.2 has not architecture-vendor-rtems target but GNAT-3.10p > has. So, I change *-coff in gcc configures for *-rtems for building the proper > gcc Makefiles. Also, there is a sintantic error in the body of RTEMS > OS-interface package (5rosinte.adb) line 147. gcc-2.8.1 does and I have not had any problems compiling native or cross gnat's using it. If you want to you gnatmake to link your programs, you will have to have the -specs option in gcc which is only in 2.8 or >. > So, you could install RTEMS and then use RTEMS as RTS for GNAT. RTEMS is > free and the new version RTEMS-4.0 is anunced as a valid RTS for GNAT. So, > if you have time you could patch the GNAT/RTEMS-3.6.0 interface or you can > wait for the RTEMS-4.0. > Also, RTEMS-3.6.0 has not POSIX timers and we implemented it. You can > find this patch at: > > ftp://caoba.datsi.fi.upm.es/pub/projects/rtems/fuentes/rtems-3.6.0-posix.patch I will look at this. We implemented this indpendently. Did you implement any of the clock_* calls? > Also, this patch contains the proper settings for compiling RTEMS-POSIX > hosted in a Red Hat 4.2 Linux targetted to a mvme135. So I guess that answers the question. The 135 BSP still works. :) --joel