source: rtems-testing/README

Last change on this file was c3096ae, checked in by Aurelio Remonda <aurelio.remonda@…>, on Sep 24, 2015 at 2:20:52 PM

Update environment README

This patch update the README file on /rtems-testing:
*Added comments about bootstrap and RTEMS building steps.
*Added comments about RTEMS test samples.
*Updated binutils, newlib and gcc repositories using git now.
*Updated gdb, autoconf and automake repositories using ftp sites now.

  • Property mode set to 100644
File size: 4.9 KB
Line 
1This package contains a collection of scripts and support files
2that support running the GCC (http://gcc.gnu.org) testsuite for
3C, C++, Ada, FORTRAN, GCJ, Go, and Objective-C.
4
5This testing environment is used on the GCC Compile Farm as well
6as at OAR.
7
8Source Code and Patches
9=======================
10You are responsible for downloading all the tools and setting up the
11source. And it should look something like this:
12
13TESTROOT
14  - gcc SOURCE directory
15  - gdb SOURCE directory
16  - rtems SOURCE directory
17  - automake SOURCE directory
18  - autoconf SOURCE directory
19  - binutils SOURCE directory
20  - newlib SOURCE directory
21  - rtems-testing (this package)
22
23Update rtems-testing/VERSIONS to point to the appropriate directories
24and versions.
25
26If the various source directories contain a CVS subdirectory,
27then they will be updated using CVS.
28
29If the various source directories contain a .svn subdirectory,
30then they will be updated using svn.
31
32Look near the top of do_one for a number of environment variables
33such as whether to build binutils and gdb from source or just
34copy the RPM contents to the working install point.
35
36do_one in this directory has a LOT of options to control what to do.
37
38You will need a toolchain to bootstrap and build RTEMS. This toolchain can be
39in turn build using rtems-source-builder.
40Once you've built the toolchain, add its 'bin' directory to $PATH, as follows:
41export PATH=/path/to/toolchain/bin:${PATH}
42Make sure you run the bootstrap script on the RTEMS source directory before
43running do_one -r.
44
45do_one -r will build RTEMS and its sample programs.
46You can use the samples to make sure the test runner works for your board.
47I.e you can run:
48~/rtems-testing/sim-scripts/realview_pbx_a9_qemu -i ticker.exe
49and see if the results make sense. You may notice the ticker sample will run
50faster than "real time" because it's a simulation, and fast idle is enabled
51by default.
52
53
54How to Setup a Source Tree For Testing
55======================================
56# Make sure test bin directories are in your PATH
57# Add compiled tools install directory
58export PATH=${HOME}/test-gcc/install/bin:${PATH}
59# Add simulator scripts install directory
60export PATH=${HOME}/test-gcc/rtems-testing/bin:${PATH}
61
62mkdir ~/test-gcc
63cd ~/test-gcc
64
65# test script infrastructure
66git clone git://git.rtems.org/rtems-testing.git
67make -C rtems-testing/sim-scripts
68
69# rtems
70git clone git://git.rtems.org/rtems.git
71
72# binutils
73git clone git://sourceware.org/git/binutils.git
74
75# newlib
76git clone git://sourceware.org/git/newlib-cygwin.git
77
78# gdb
79wget ftp://ftp.gnu.org/gnu/gdb/gdb-7.10.tar.xz
80tar -xvf gdb-7.10.tar.xz
81rm gdb-7.10.tar.xz
82
83# gcc
84git clone git://gcc.gnu.org/git/gcc.git gcc-git
85
86# symlink newlib into gcc-svn
87cd gcc-svn
88ln -s ~/test-gcc/newlib-cygwin/src/newlib .
89ln -s ~/test-gcc/newlib-cygwin/src/libgloss .
90cd ..
91
92# obtain automake and autoconf from ftp.gnu.org as tarballs
93# NOTE: Check versions required for RTEMS CVS.
94wget http://ftp.gnu.org/gnu/autoconf/autoconf-2.69.tar.xz
95tar -xvf autoconf-2.69.tar.xz
96wget http://ftp.gnu.org/gnu/automake/automake-1.15.tar.xz
97tar -xvf automake-1.15.tar.xz
98
99# make install points
100mkdir install
101mkdir bsp-install
102mkdir log
103
104### Verify the file VERSIONS matches your installation.
105=========================================
106
107x86_64 Host
108============
109
110You will likely need the 32 bit glibc development kit.  If you do not
111have this you will get an error like the following while building gcc:
112
113gnu/stubs-32.h: No such file or directory
114
115Fedora 10: yum install glibc-devel
116
117DejaGNU
118========
119
120Fedora 10: Install dejagnu RPM.
121
122MPFR/GMP
123========
124
125You must have a sufficiently recent version of GMP and MPFR to build
126GCC.  On some OSes you can install a standard package.  On others,
127you may have to provide your own installation.
128
129Fedora 10: Install mpfr-devel RPM.
130
131GNAT
132====
133
134You must have a native GNAT installed.  .  On some OSes you can
135install a standard package.  On others, you may have to provide
136your own installation.  The first step in the build process is
137building a native compiler with potentially C, C++ and Ada support.
138This compiler will be used for all subsequent cross tool builds.
139
140Fedora 10: Install gcc-gnat RPM.
141
142
143DejaGNU Support Files
144=====================
145
146${HOME}/.dejagnurc may point dejagnu to another location.
147
148      set boards_dir /home/joel/dejagnu/boards
149
150The scripts in this directory use their own dejagnu/boards support.
151
152Ada ACATS Testing Support Files
153===============================
154
155The files in gcc/testsuite/ada/acats/ directory support
156that directory in the gcc source tree.
157
158C/C++ Support Files
159======================
160
161The files rtems_gcc_main.c and rundeja in the top directory
162support the gcc/testsuite subdirectory in the gcc source tree.
163
164Skyeye Installation
165===================
166
16715 Jan 2009: 1.2.7 does not work with RTEMS. Unknown reason.  Use 1.2.5
168  until this is resolved.
169
170mkdir ~/skyeye
171cd ~/skyeye
172svn co https://skyeye.svn.sourceforge.net/svnroot/skyeye/skyeye-v1/branches/skyeye-1.2.5/
173cd skyeye-1.2.5
174./configure
175make
Note: See TracBrowser for help on using the repository browser.