Re: [web] Revised instructions for testing using a simulator

[Janis Johnson <janis187 at us dot ibm dot com>]

Zack,

I like the suggestions of showing both ways of making combined trees:
including gcc in the tools tree, or linking two separate CVS trees.
It makes the howto somewhat more complicated, but makes life easier for
people doing whichever method wouldn't be documented otherwise.

Using a separate tree for GCC and then making a combined tree with links
allows using the same tools tree with multiple versions of GCC, e.g.,
for testing the mainline and then a branch.  (I've never actually done
that but it sounds useful.)  It also allows using anoncvs for tools but
a writable CVS tree for GCC.

It doesn't work to get "naked-gdb" from cvs/src, so that trick of
getting only what's needed requires the use of uberbaum.  I forgot to
check the size of my old setup, but this seems to save lots of space.

Phil mentioned using symlink-tree; how does that fit in with updates?

Zack wrote:
> Janis wrote:
> > I'll stay out of the discussion about where it's appropriate to get CVS
> > trees.  If the decision is to stay with the currently suggested ones and
> > create a combined tree using hard links, there should be a new section
> > explaining how to update the trees and the combined directory.  I can
> > write up how I do it.
> 
> Yeah, I'd really appreciate your writeup here.  As I explained to Ben
> downthread, this is the operation that doesn't work for me.

I've appended some scripts to set up a combined tree out of separate CVS
trees, which I've verified work for me.  Chunks of this code can go into
simtest-howto.html, with whatever modifications you want.

> > The "Verified" column could have a link to archived test results.  Even
> > if those aren't updated very often, knowing which tests failed at one
> > time is more useful than knowing the number of tests that failed at one
> > time.
> 
> We don't currently have these - but in a fit of insanity I scripted my
> computer to try to build and test every last one of them.  So we will
> have them shortly, and yes, that's an excellent idea.

Wonderful!  Thanks for doing that, and for fixing this document.

Janis

------------------------------------------------------------------------
#! /bin/sh

# mkviews -- Set up new CVS trees for GCC and and GNU toolchain.

parent=`pwd`

cd ${parent}
rm -rf gcc
mkdir gcc
cd gcc
CVSROOT=":pserver:anoncvs@subversions.gnu.org:/cvsroot/gcc"
export CVSROOT
echo "password is empty string; enter that on prompt"
cvs -z 9 login
cvs co gcc > co.log 2>&1
cvs logout

echo
cd ${parent}
rm -rf src
mkdir src
mkdir src/src
cd src/src
SRCROOT=":pserver:anoncvs@sources.redhat.com:/cvs/uberbaum"
echo "password is 'anoncvs'; enter that on prompt"
cvs -z 9 -d ${SRCROOT} login
cvs -d ${SRCROOT} co \
  binutils sim newlib naked-gdb readline dejagnu > ../co.log 2>&1
cvs -d ${SRCROOT} logout
------------------------------------------------------------------------
#! /bin/sh

# mkupdate -- Update existing GCC and tools CVS trees.

LOG="../`date +%Y%m%d`.log"
parent=`pwd`

cd ${parent}/gcc/gcc
CVSROOT=":pserver:anoncvs@subversions.gnu.org:/cvsroot/gcc"
export CVSROOT
echo "password is empty string; enter that on prompt"
cvs -z 9 login
touch ${LOG}
contrib/gcc_update >> ${LOG} 2>&1
cvs logout

echo
cd ${parent}/src/src
SRCROOT=":pserver:anoncvs@sources.redhat.com:/cvs/uberbaum"
echo "password is 'anoncvs'; enter that on prompt"
cvs -z 9 -d ${SRCROOT} login
touch ${LOG}
cvs -d ${SRCROOT} co binutils sim newlib naked-gdb readline dejagnu \
  >> ${LOG} 2>&1
cvs -d ${SRCROOT} logout
------------------------------------------------------------------------
#! /bin/sh

# mkcombined -- Make a combined tree using hard links to the CVS trees.

parent=`pwd`

cd ${parent}
rm -rf combined
mkdir combined
cd ${parent}/src/src
find . -print | cpio -pdlm ../../combined
cd ${parent}/gcc/gcc
find . -print | cpio -pdlmu ../../combined
------------------------------------------------------------------------