[pooma-dev] Problem checking the build of gcc

[Jeffrey Oldham]

On Wed, Jun 06, 2001 at 11:41:29AM -0600, Dave Nystrom wrote:
> Hi Jeffrey,
> 
> Here is the build log from my attempt to perform the checks of my gcc build.
>
> saltydog % pwd
> /home/wdn/packages/tmp/gcc-3.0-20010527/objdir/gcc
> ...
> `if [ -f ${srcdir}/../dejagnu/runtest ] ; then echo ${srcdir}/../dejagnu/runtest ; else echo runtest; fi` --tool g77 )
> /bin/sh: runtest: command not found
> ...
> fi
> /bin/sh: runtest: command not found
> make: [check-g++] Error 127 (ignored)

runtest is part of the dejagnu tool used to perform the gcc regression
tests.  The easiest thing is to omit running the regression tests.

If you do want to run the tests and you are willing to build some more
infrastructure by installing dejagnu, follow these instructions:

1. Download the most recent copy of dejagnu.  Read
`http://www.gnu.org/software/dejagnu/dejagnu.html#TOCdownloading' how
to access the CVS tree.

2. Configure for compilation.
   cd dejagnu		# the root of the directory that was downloaded
   mkdir objdir		# always better to compile in a separate directory
   cd objdir
   declare -x CC=${HOME}/gcc-install/gcc1/bin/gcc
   declare -x CXX=${HOME}/gcc-install/gcc1/bin/g++
   declare -x LD_LIBRARY_PATH=/home/oldham/gcc-install/gcc1/lib
   ../configure linux --srcdir .. --prefix ${HOME}/bin

Change the paths to the location of your C and C++ compilers.  I
recommend using your gcc 3.0 installation.  Change the `--prefix' to
wherever you want the results to be installed.

3. Compile.

   make CC=${CC} CXX=${CXX}

(I forget how to check the code.)

4. Install.

   make install

Thanks,
Jeffrey D. Oldham
oldham at codesourcery.com