No rule to make target all in gcc/f/runtime

[Robert Lipe]

> 1. command for updating cvs-tree
>      cvs [-z9] update  egcs || cvs [ -z9 ]co egcs
>     (Y/N)

I highly recommend the -z9 flag unless you happen to be inside Cygnus
HQ in Mountain View. :-)

I just cd into the top level egcs directory and do a 'cvs update'.  CVS
knows that an EGCS tree already lives here (CVS/*) and I have -z9 in my
~/.cvsrc so I never have to type it again.

>  2. software, which nessesory on SCO OS 5.04:
>      gnu-path + gmake +autoconf + m4 + bison + flex + native as + native ld +

I don't know what "gnu-path" is.

Autoconf, m4, bison, and flex are necessary only for snapshots.   A 
"normal" user wouldn't need these.    If you're poking at snaps, that
list is about correct, I think.   Of course, if you're willing to manually
dink with timestamps on the generated files that are committed, you could
circumvent the need for those four even when developing, too.

> (gcc-2.7.2.1 or egcs-1.0.1)
>            2.5           2.6           (last)
>     Something else ?

EGCS correctly bootstraps with the OpenServer native compiler (which 
I've probably done a billion times) but since the 1.0.1 release, I've 
been using egcs 1.0.1 instead just to shake things up a little.

>     /usr/local/bin must be the first directory in $PATH

It does simplify things, yes.

>  3. configure process:
>     1, mkdir egcs-obj near egcs
>      2. cd egcs-obj; sh ../../configure --srcdir=../../
> [other-possibly-options]
> 
>  May be the problem, that srcdir must be absolute ?

Looking in my negcs (native egcs, which is my play space) directory,
I see that I've always configured it relative with the command:
	../egcs/configure

I don't know if this matters.

>  4. building process
>     make bootstrap
>     make install

Right.

-- 
Robert Lipe       http://www.dgii.com/people/robertl       robertl@dgii.com