This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [web] Revised instructions for testing using a simulator
- From: Phil Edwards <phil at jaj dot com>
- To: Janis Johnson <janis187 at us dot ibm dot com>
- Cc: Zack Weinberg <zack at codesourcery dot com>, gcc-patches at gcc dot gnu dot org, Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>, Fergus Henderson <fjh at cs dot mu dot oz dot au>
- Date: Wed, 25 Sep 2002 13:29:56 -0400
- Subject: Re: [web] Revised instructions for testing using a simulator
- References: <20020924235003.GK5021@codesourcery.com> <20020925101439.A13844@us.ibm.com>
On Wed, Sep 25, 2002 at 10:14:39AM -0700, Janis Johnson wrote:
> On Tue, Sep 24, 2002 at 04:50:03PM -0700, Zack Weinberg wrote:
> > Here is a revised version of simtest-howto.html. The two biggest
> > changes are: First, I replaced the directions for creating a combined
> > tree with hard links -- which in my experience has never worked
> > properly -- with directions for checking out a pre-combined tree from
> > the "uberbaum" repository.
>
> The current instructions work for me. I update the gcc tree using
> contrib/gcc_update, and the the others using "cvs update", although I'll
> try using "cvs co" instead. (Is there something like gcc_update for
> updating the src tree, or things that can go wrong because of the lack
> of such a tool?) After an update I remove the old combined tree (full
> of hard links) and create a new one. The new information about checking
> out directories that don't take as much room is good.
Likewise, although I've always used symbolic links, based on a script I
hashed together long ago. (Actually uses gcc's own symlink_tree script.)
This way I could tell more easily which version (GCC or src) of a file
was being used.
Phil
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002