AW: AW: AW: [Mono-list] Daily build errors
Jochen Wezel (CompuMaster GmbH)
jwezel@compumaster.de
Fri, 29 Oct 2004 10:03:04 +0200
Hi gennady!
Make uninstall and make clean worked fine, but make bootstrap-clean =
leads to an error:
rm -f "libmonogc.la/so_locations"
rm -f "libmonogc-static.la/so_locations"
rm -f *.o core *.core
rm -f *.lo
make[2]: Verlassen des Verzeichnisses Verzeichnis =
=C2=BB/mono-dev/mono-cvs-auth/mono/libgc=C2=AB
make[1]: Verlassen des Verzeichnisses Verzeichnis =
=C2=BB/mono-dev/mono-cvs-auth/mono/libgc=C2=AB
Making clean in .
make[1]: Wechsel in das Verzeichnis Verzeichnis =
=C2=BB/mono-dev/mono-cvs-auth/mono=C2=AB
rm -rf .libs _libs
rm -f *.lo
make[1]: Verlassen des Verzeichnisses Verzeichnis =
=C2=BB/mono-dev/mono-cvs-auth/mono=C2=AB
cd ./../mcs && make clean-profiles
make[1]: Wechsel in das Verzeichnis Verzeichnis =
=C2=BB/mono-dev/mono-cvs-auth/mcs=C2=AB
make profile-do--default--clean profile-do--net_2_0--clean
make[2]: Wechsel in das Verzeichnis Verzeichnis =
=C2=BB/mono-dev/mono-cvs-auth/mcs=C2=AB
make PROFILE=3Ddefault clean
make[3]: Wechsel in das Verzeichnis Verzeichnis =
=C2=BB/mono-dev/mono-cvs-auth/mcs=C2=AB
*** You need a C# compiler installed to build MCS. (make sure mcs works =
from the command line)
*** Read INSTALL.txt for information on how to bootstrap
*** a Mono installation.
make[3]: *** [platform-check] Fehler 1
make[3]: Verlassen des Verzeichnisses Verzeichnis =
=C2=BB/mono-dev/mono-cvs-auth/mcs=C2=AB
make[2]: *** [profile-do--default--clean] Fehler 2
make[2]: Verlassen des Verzeichnisses Verzeichnis =
=C2=BB/mono-dev/mono-cvs-auth/mcs=C2=AB
make[1]: *** [clean-profiles] Fehler 2
make[1]: Verlassen des Verzeichnisses Verzeichnis =
=C2=BB/mono-dev/mono-cvs-auth/mcs=C2=AB
make: *** [mcs-do-clean-profiles] Fehler 2
[root@lwezel mono]#
A following make aborts again:
make[3]: Wechsel in das Verzeichnis Verzeichnis =
=C2=BB/mono-dev/mono-cvs-auth/mono/runtime=C2=AB
test -f ../../mcs/monoresgen/monoresgen.exe
make[3]: *** [monoresgen.exe] Fehler 1
make[3]: Verlassen des Verzeichnisses Verzeichnis =
=C2=BB/mono-dev/mono-cvs-auth/mono/runtime=C2=AB
make[2]: *** [all-recursive] Fehler 1
make[2]: Verlassen des Verzeichnisses Verzeichnis =
=C2=BB/mono-dev/mono-cvs-auth/mono/runtime=C2=AB
make[1]: *** [all-recursive] Fehler 1
make[1]: Verlassen des Verzeichnisses Verzeichnis =
=C2=BB/mono-dev/mono-cvs-auth/mono=C2=AB
Regards
Jochen
-----Urspr=FCngliche Nachricht-----
Von: gennady wexler [mailto:adyler@winisp.net]=20
Gesendet: Donnerstag, 28. Oktober 2004 20:53
An: Jochen Wezel (CompuMaster GmbH); Paul; mono
Betreff: Re: AW: AW: [Mono-list] Daily build errors
add this to your build commands:
make uninstall
make clean
make bootstrap-clean
On 10/28/04 9:47 AM, "Jochen Wezel (CompuMaster GmbH)"
<jwezel@compumaster.de> wrote:
> Hi Paul,
>=20
> I needed to update my mono runtime because I cannot compile via CVS.
>=20
> In folder mono, I started with:
>=20
> ./autogen.sh --prefix=3D/usr
> make
>=20
>=20
> make install
> [......]
> /bin/sh ../../mkinstalldirs /usr/lib/mono/1.0 /usr/bin/install -c -m=20
> 644 mscorlib.dll /usr/lib/mono/1.0/mscorlib.dll /usr/bin/install -c -m =
> 644 ./mscorlib.dll.mdb /usr/lib/mono/1.0/mscorlib.dll.mdb
> MONO_PATH=3D. ../../mono/mini/mono --config ../../data/config=20
> ./../gacutil.exe /i ./Accessibility.dll /f /package 1.0 /gacdir=20
> /usr/lib /root /usr/lib Corlib not in sync with this runtime: expected =
corlib version 28, found 26.
> Download a newer corlib or a newer runtime at =
http://www.go-mono.com/daily.
> make[3]: *** [install-data-local] Fehler 1
> make[3]: Verlassen des Verzeichnisses Verzeichnis=20
> =C2=BB/mono-dev/mono-cvs-auth/mono/runtime/net_1_1=C2=AB
> make[2]: *** [install-am] Fehler 2
> make[2]: Verlassen des Verzeichnisses Verzeichnis=20
> =C2=BB/mono-dev/mono-cvs-auth/mono/runtime/net_1_1=C2=AB
> make[1]: *** [install-recursive] Fehler 1
> make[1]: Verlassen des Verzeichnisses Verzeichnis=20
> =C2=BB/mono-dev/mono-cvs-auth/mono/runtime=C2=AB
> make: *** [install-recursive] Fehler 1
>=20
>=20
> For testing purposes, I also started that:
>=20
> [root@lwezel mono]# make bootstrap
> rm -f ./../mcs/mcs/mcs.exe ./../mcs/class/lib/default/mscorlib.dll
> ./../mcs/class/lib/default/System.dll
> ./../mcs/class/lib/default/System.Xml.dll
> ./../mcs/class/lib/default/Mono.CompilerServices.SymbolWriter.dll
> for dir in jay mcs class/corlib class/System; do \
> (cd ./../mcs/$dir && make PROFILE=3Ddefault NO_SIGN_ASSEMBLY=3Dyes=20
> USE_BOOT_COMPILE=3Dyes BOOTSTRAP_MCS=3D"mcs -d:BOOTSTRAP_WITH_OLDLIB") =
||=20
> exit 1 ; \ done
> make[1]: Wechsel in das Verzeichnis Verzeichnis=20
> =C2=BB/mono-dev/mono-cvs-auth/mcs/jay=C2=AB
> make all-local
> make[2]: Wechsel in das Verzeichnis Verzeichnis=20
> =C2=BB/mono-dev/mono-cvs-auth/mcs/jay=C2=AB
> make[2]: F=C3=BCr das Target =C2=BBall-local=C2=AB gibt es nichts zu =
tun.
> make[2]: Verlassen des Verzeichnisses Verzeichnis=20
> =C2=BB/mono-dev/mono-cvs-auth/mcs/jay=C2=AB
> make[1]: Verlassen des Verzeichnisses Verzeichnis=20
> =C2=BB/mono-dev/mono-cvs-auth/mcs/jay=C2=AB
> make[1]: Wechsel in das Verzeichnis Verzeichnis=20
> =C2=BB/mono-dev/mono-cvs-auth/mcs/mcs=C2=AB
> make all-local
> make[2]: Wechsel in das Verzeichnis Verzeichnis=20
> =C2=BB/mono-dev/mono-cvs-auth/mcs/mcs=C2=AB
> mcs -d:BOOTSTRAP_WITH_OLDLIB -d:NET_1_1 -d:ONLY_1_1 -g /target:exe
> /out:mcs.exe cs-parser.cs @mcs.exe.sources Corlib not in sync with=20
> this runtime: expected corlib version 28, found 22.
> Download a newer corlib or a newer runtime at =
http://www.go-mono.com/daily.
> make[2]: *** [mcs.exe] Fehler 1
> make[2]: Verlassen des Verzeichnisses Verzeichnis=20
> =C2=BB/mono-dev/mono-cvs-auth/mcs/mcs=C2=AB
> make[1]: *** [all.real] Fehler 2
> make[1]: Verlassen des Verzeichnisses Verzeichnis=20
> =C2=BB/mono-dev/mono-cvs-auth/mcs/mcs=C2=AB
> make: *** [mcs-do-basic-build] Fehler 1 [root@lwezel mono]#
>=20
>=20
> I'm wondering why it finds sometimes runtime version 22, and the next=20
> time 26...
>=20
> In any case, this is the cause why I tried to build from the "daily =
builds"
> completely new.
>=20
> I also have tried to remove anything which has been installed with=20
> mono (/usr and /usr/local). This helped last time when there was mono=20
> installed in /usr and in another version in /usr/local. After this, I=20
> removed all mono-packages with red carpet and then reinstalled them =
again to get a working start point.
> But it hasn't helped this time :(
> [root@lwezel mono-cvs-auth]# cat cleanupmonoinstallation.sh #!/bin/sh=20
> cd /usr rm -f -R -d bin/*.exe bin/*.dll bin/mbas* bin/mcs* bin/mono*=20
> bin/libmono*
> bin/libmint* lib/mono include/mono etc/mono share/mono cd /usr/local=20
> rm -f -R -d bin/*.exe bin/*.dll bin/mbas* bin/mcs* bin/mono*=20
> bin/libmono*
> bin/libmint* lib/mono include/mono etc/mono share/mono [root@lwezel=20
> mono-cvs-auth]#
>=20
>=20
> -----Urspr=FCngliche Nachricht-----
> Von: mono-list-admin@lists.ximian.com
> [mailto:mono-list-admin@lists.ximian.com] Im Auftrag von Paul
> Gesendet: Donnerstag, 28. Oktober 2004 17:47
> An: Mono List
> Betreff: Re: AW: [Mono-list] Daily build errors
>=20
> Hi,
>=20
>>> First - why are you doing this as root? Root is there for a purpose
>> and it
>>> isn't just so you don't have to keep typing su to change to it. On a =
>>> machine, it can be considered a major deity. It has the power of=20
>>> life,
>>=20
>>> death and existance on a box. Mess something up as root and you can=20
>>> (and probably *will*) do some serious damage!
>> As in the real world: if you have rights you can missuse them. If you =
>> don't have any rights, you can't do your job.
>=20
> You've missed the point. You do everything as a user and until you=20
> need to (for instance, installing into a directory owned by root, such =
> as /usr or /var), you stay like that. As a user, you have all the =
rights you need.
>=20
>>> Second, is this a compile from cvs and if it is, is it via and=20
>>> update and if it is from an update, what happens if you ditch that=20
>>> version of
>>=20
>>> mono/mcs and do a fresh checkout?
>> This is a compile from the "daily build" downloaded from the mono=20
>> website. Nothing CVS or similar.
>=20
> Try the cvs route - it's much easier to bugtrack!
>=20
>>> Third, what distro are you using? I know with Fedora Core, things
>> aren't
>>> always happy in that /usr/local/lib/pkgconfig isn't always checked - =
>>> this could be something similar.
>> Sorry, I had really forgotten this important information. Here it is:
>> RedHat 9
>=20
> RH9 was fine with pkgconfig in /usr/local/lib
>=20
>>> Fourth, when you ran autogen.sh, did you specify anything with --
>> prefix=3D?=20
>>> (ie. --prefix=3D/usr). Again, problems can occur if you're in as =
root=20
>>> or
>>=20
>>> have specified somewhere insane for your libraries and apps to live.
>> I used following lines:
>> ./autogen.sh --prefix=3D/usr
>> make
>> make install <---- here it crashes because of the
>> missing file
>=20
> As I say, use the cvs route. Full instructions are at
>=20
> http://www.all-the-johnsons.co.uk/mono/mono-compiling.html
>=20
> TTFN
>=20
> Paul
> --
> "Trust me, I know what I'm doing" - Det. Sledgehammer=20
> _______________________________________________
> Mono-list maillist - Mono-list@lists.ximian.com=20
> http://lists.ximian.com/mailman/listinfo/mono-list