Hi,
"Jochen Wezel (CompuMaster GmbH)" <[EMAIL PROTECTED]> writes:
> Now I removed my complete old content of my CVS folder and checked out again.
>
> export CVS_RSH=ssh
> export [EMAIL PROTECTED]:/cvs/public
> rm -f -R -d mcs mono xsp monkeyguide monocov
> cvs -z3 co mcs mono xsp monkeyguide monocov
> cd mono
> ./autogen.sh --prefix=/usr
> make
You need to use some form of bootstrapping. I'm working on a patch that
will do the bootstrap automatically, but for now, on a fresh checkout
from CVS, you _need_ to use 'make bootstrap' or 'make monolite-bootstrap'.
> This is the new and well-known error message:
>
> Making all in runtime
> make[2]: Wechsel in das Verzeichnis Verzeichnis
> »/mono-dev/mono-cvs-auth/mono/runtime«
> Making all in .
> make[3]: Wechsel in das Verzeichnis Verzeichnis
> »/mono-dev/mono-cvs-auth/mono/runtime«
> test -f ../../mcs/monoresgen/monoresgen.exe
> make[3]: *** [monoresgen.exe] Fehler 1
> make[3]: Verlassen des Verzeichnisses Verzeichnis
> »/mono-dev/mono-cvs-auth/mono/runtime«
> make[2]: *** [all-recursive] Fehler 1
> make[2]: Verlassen des Verzeichnisses Verzeichnis
> »/mono-dev/mono-cvs-auth/mono/runtime«
> make[1]: *** [all-recursive] Fehler 1
> make[1]: Verlassen des Verzeichnisses Verzeichnis »/mono-dev/mono-cvs-auth/mono«
> make: *** [all] Fehler 2
It's saying: the command
test -f ../../mcs/monoresgen/monoresgen.exe
failed. It failed because that file doesn't exist. That file doesn't
exist because you didn't build in the 'mcs' tree. If you use one of the
bootstrapping targets ('bootstrap' or 'monolite-bootstrap'), it
automatically builds in the 'mcs' tree in the right order.
- Hari
_______________________________________________
Mono-list maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-list