source: rtems-testing/README @ 8da8788

4.11
Last change on this file since 8da8788 was 1273785, checked in by Joel Sherrill <joel.sherrill@…>, on May 15, 2012 at 9:03:18 PM

rtems-testing - Remove CVS Ids (scripted)

  • Property mode set to 100644
File size: 4.8 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 setting up the source. And it should look
11something 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
38How to Setup a Source Tree For Testing
39======================================
40# Make sure test bin directories are in your PATH
41# Add compiled tools install directory
42export PATH=${HOME}/test-gcc/install/bin:${PATH}
43# Add simulator scripts install directory
44export PATH=${HOME}/test-gcc/rtems-testing/bin:${PATH}
45
46mkdir ~/test-gcc
47cd ~/test-gcc
48cvs -z 9 -d :pserver:anoncvs@sourceware.org:/cvs/src login
49cvs -z 9 -d :pserver:anonymous@www.rtems.org:/usr1/CVS login
50
51# test script infrastructure
52cvs -z 9 -d :pserver:anonymous@www.rtems.org:/usr1/CVS co -P rtems-testing
53make -C rtems-testing/sim-scripts
54
55# rtems
56cvs -z 9 -d :pserver:anonymous@www.rtems.org:/usr1/CVS co -P rtems
57
58# binutils
59mkdir binutils-cvs
60cd binutils-cvs
61READ ONLY: cvs -z 9 -d :pserver:anoncvs@sourceware.org:/cvs/src co binutils
62WRITE: CVS_RSH=ssh cvs -d :ext:joel@sourceware.org:/cvs/src co -P binutils
63cd ..
64
65# newlib
66mkdir newlib-cvs
67cd newlib-cvs
68READ ONLY: cvs -z 9 -d :pserver:anoncvs@sourceware.org:/cvs/src co newlib
69WRITE: CVS_RSH=ssh cvs -d :ext:joel@sourceware.org:/cvs/src co -P newlib
70cd ..
71
72# gdb
73mkdir gdb-cvs
74cd gdb-cvs
75READ ONLY: cvs -z 9 -d :pserver:anoncvs@sourceware.org:/cvs/src co gdb
76WRITE: CVS_RSH=ssh cvs -d :ext:joel@sourceware.org:/cvs/src co -P gdb
77cd ..
78
79# gcc
80READ ONLY: svn checkout svn://gcc.gnu.org/svn/gcc/trunk gcc-svn
81WRITE      svn co svn+ssh://joel@gcc.gnu.org/svn/gcc/trunk gcc-svn
82
83# symlink newlib into gcc-svn
84cd gcc-svn
85ln -s ~/test-gcc/newlib-cvs/src/newlib .
86ln -s ~/test-gcc/newlib-cvs/src/libgloss .
87cd ..
88
89# obtain automake and autoconf from ftp.gnu.org as tarballs
90# NOTE: Check versions required for RTEMS CVS.
91wget ftp://ftp.gnu.org/pub/gnu/autoconf/autoconf-2.63.tar.bz2
92tar xjf autoconf-2.63.tar.bz2
93wget ftp://ftp.gnu.org/pub/gnu/automake/automake-1.10.2.tar.bz2
94tar xjf automake-1.10.2.tar.bz2
95
96# make install points
97mkdir install
98mkdir bsp-install
99mkdir log
100
101### Verify the file VERSIONS matches your installation.
102=========================================
103
104x86_64 Host
105============
106
107You will likely need the 32 bit glibc development kit.  If you do not
108have this you will get an error like the following while building gcc:
109
110gnu/stubs-32.h: No such file or directory
111
112Fedora 10: yum install glibc-devel
113
114DejaGNU
115========
116
117Fedora 10: Install dejagnu RPM.
118
119MPFR/GMP
120========
121
122You must have a sufficiently recent version of GMP and MPFR to build
123GCC.  On some OSes you can install a standard package.  On others,
124you may have to provide your own installation.
125
126Fedora 10: Install mpfr-devel RPM.
127
128GNAT
129====
130
131You must have a native GNAT installed.  .  On some OSes you can
132install a standard package.  On others, you may have to provide
133your own installation.  The first step in the build process is
134building a native compiler with potentially C, C++ and Ada support.
135This compiler will be used for all subsequent cross tool builds.
136
137Fedora 10: Install gcc-gnat RPM.
138
139
140DejaGNU Support Files
141=====================
142
143${HOME}/.dejagnurc may point dejagnu to another location.
144
145      set boards_dir /home/joel/dejagnu/boards
146
147The scripts in this directory use their own dejagnu/boards support.
148
149Ada ACATS Testing Support Files
150===============================
151
152The files in gcc/testsuite/ada/acats/ directory support
153that directory in the gcc source tree.
154
155C/C++ Support Files
156======================
157
158The files rtems_gcc_main.c and rundeja in the top directory
159support the gcc/testsuite subdirectory in the gcc source tree.
160
161Skyeye Installation
162===================
163
16415 Jan 2009: 1.2.7 does not work with RTEMS. Unknown reason.  Use 1.2.5
165  until this is resolved.
166
167mkdir ~/skyeye
168cd ~/skyeye
169svn co https://skyeye.svn.sourceforge.net/svnroot/skyeye/skyeye-v1/branches/skyeye-1.2.5/
170cd skyeye-1.2.5
171./configure
172make
Note: See TracBrowser for help on using the repository browser.