rtems version information/errata
joel at OARcorp.com
Fri Jan 19 12:01:40 UTC 2001
I am on the road and don't have easy access to check into this
much but here is what I would start with. There are gnat RPMs
for 3.13p in the snapshots directory if I recall correctly as well
as proper patches. The build scripts should be there under
ada_tools. If they are not, then I would recommend looking
at the RPM specifications (add scripts_ada at top of RTEMS tree)
and use those steps by hand.
FWIW the gnat patch breaks the sparc backend and I recall there
is some other issue like that. In general terms gcc 2.8.1 is VERY old
and does not support ELF for many embedded targets. This means
that in many ways, waiting for the heavily anticipated merger of
gnat with the current gcc is good.
I worked with Laurent Guerby to run ACATS on at least one target
and there are scripts to do that on OARs ftp site.
lange92 at 2067.resnet.uni.edu wrote:
> Hi all,
> I'm trying to install RTEMS-4.5.0 and gnat3.13 on a linux
> system. However, I'm having a good bit of difficulty trying to figure out
> what exactly is going on with the bit_ada script. I was unable to find an
> ada_build_scripts.tar.gz in the 4.5.0 release, and decided that my best
> bet was to use the one from the 4.0 release instead.
> I am now compiling on a linux-from-scratch machine, using gcc-2.8.1 and
> gnat-3.13 to compile. Installed in my root filesystem are binutils-2.10,
> glibc-2.1.3, libtool-1.3.5, bin86-0.15.1, and ld.so-1.9.9. gcc-2.8.1 and
> gnat-3.13p are in the default locations, as per the instructions.
> I tried installing on a Debian system, but gave up on that because even
> though the system passed the `gnatmake hello.adb` test on the web page,
> the compile failed with dozens of errors, indicating that gcc didn't
> support the various "--gnat" flags.
> So anyway, what are the correct files to compile together? I currently
> have the following files in my oar/archive directory:
> I know there are many files in there relating to the gnat-3.12p
> installation, but I was careful to prepare for the bit_ada script using
> only the 3.13 files. Everything patched fine, and I don't have any .rej
> files anywhere in the build directories. However, compilation fails with
> the following output:
> ../varasm.o: In function `initializer_constant_valid_p':
> ../varasm.o(.text+0x5d0c): multiple definition of `initializer_constant_valid_p'
> typeck2.o(.text+0x4d4): first defined here
> ld: Warning: size of symbol `initializer_constant_valid_p' changed from 760 to 792 in ../varasm.o
> make: *** [../cc1plus] Error 1
> make: Leaving directory `/mnt/home/lange92/oar/tools/build-i386-elf-tools/gcc/cp'
> make: *** [cc1plus] Error 2
> make: Leaving directory `/mnt/home/lange92/oar/tools/build-i386-elf-tools/gcc'
> make: *** [all-gcc] Error 2
> ERROR: **** FAILED **** base build of C and C++ (step 1)
> Started: Fri Jan 19 02:24:38 CST 2001
> Finished: Fri Jan 19 02:45:43 CST 2001
> I did notice that the gnat/rtems documentation has not been updated
> since 4.5.0-beta3 was released as 4.5.0, and there were some interesting
> challenges locating some of the files, but other than that, things looked
> okay until the compile failed. I also noticed that the gcc-281.dif file
> that comes with gnat-3.13 patched the varasm.c file that wouldn't
> satisfactorily assemble.
> What are the proper files and versions to build with? Should I try to go
> with the 4.0.0 version or the 4.5.0 version? And should I use gnat-3.12 or
> On a more personal note, I would like to get RTEMS to successfully
> compile once, because I'm hoping to use RTEMS for the project we're
> working on in class. My professor is developing a computer-controlled
> train set, and I would prefer to build our controlling programs using
> RTEMS, because it appears to be a considerably more mature project than
> the MaRTE executive that is otherwise planned for use in class. Plus, the
> documentation suggests that RTEMS has networking support, which could
> prove very useful in the train project. (I personally would like to build
> a remote-control for the train set, so it could be remotely and viewed
> using a webcam, for example.) The target I'm trying to build for is an
> i386 machine...
> I see several files for sparc and ppc targets, in at least .rpm
> format. Does anyone have a working, precompiled, version of RTEMS for the
> i386 (preferably i386-elf) platform, that could be easily installed
> without hassling with the compilation?
> Thanks for the input.
> Daniel Lange
More information about the users