source: rtems-testing/README @ 67e2e75

4.11
Last change on this file since 67e2e75 was e6a5d77, checked in by Joel Sherrill <joel.sherrill@…>, on Jan 14, 2012 at 8:18:10 AM

Update to add initial support for git.

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