What steps will reproduce the problem? 1. Compile mono in a tinderbox on FreeBSD-CURRENT

What is the expected output? What do you see instead?

Compilation freezes:

if test -w ../mcs; then :; else chmod -R +w ../mcs; fi cd ../mcs && gmake NO_DIR_CHECK=1 PROFILES='default net_2_0 net_3_5 net_2_1' CC='cc' all-profiles gmake[3]: Entering directory /usr/ports/lang/mono/work/mono-2.0.1/mcs' gmake profile-do--default--all profile-do--net_2_0--all profile-do--net_3_5--all profile-do--net_2_1--all gmake[4]: Entering directory/usr/ports/lang/mono/work/mono-2.0.1/mcs' gmake PROFILE=basic all gmake[5]: Entering directory /usr/ports/lang/mono/work/mono-2.0.1/mcs' gmake[6]: *** [build/deps/basic-profile-check.exe] Error 1 gmake[6]: Entering directory/usr/ports/lang/mono/work/mono-2.0.1/mcs' * The compiler 'false' doesn't appear to be usable. * Trying the 'monolite' directory. gmake[7]: Entering directory `/usr/ports/lang/mono/work/mono-2.0.1/mcs'

^Cgmake[8]: * [build/deps/basic-profile-check.exe] Interrupt: 2 gmake[7]: [do-profile-check] Interrupt: 2 gmake[6]: [do-profile-check-monolite] Interrupt: 2 gmake[5]: [do-profile-check] Interrupt: 2 gmake[4]: [profile-do--basic--all] Interrupt: 2 gmake[3]: [profiles-do--all] Interrupt: 2 gmake[2]: [all-local] Interrupt: 2 gmake[1]: * [all-recursive] Interrupt: 2

Please use labels and text to provide additional information.

Reported by paulbeard@gmail.com

It also hangs building on 6.3-RELEASE and 6.2-RELEASE. According to ^T mono process is hang in [ksesigwait] state. Pstree (sysutils/pstree) output regarding portbuild in attached file.

And another note - it builds successfully on 7.1-STABLE (sources from Feb 7).

I can't reporduce this un CURRENT... The FreeBSD tinderbox seems to compile mono successfully too.

The configuration where I compile mono-2.0.1: - uname: FreeBSD trilian.sigabrt.org 8.0-CURRENT FreeBSD 8.0-CURRENT #0 r189024M: Wed Feb 25 13:26:20 CET 2009
root@trilian.sigabrt.org:/usr/obj/usr/src/sys/GENERIC i386 - all mono dependencies (make missing) installed using packages ~2 weeks ago.

Some times ago, I was not able to update mono when mono-applications (e.g. tomboy) where running... Do you have any mono process running while compiling? Can you try outside of a tinderbox?

Regards, Romain

Can confirm mono 2.0.1 and 2.4_2 build fine on -CURRENT too.

Can confirm fail on 6.3-STABLE FreeBSD

[xxx@yyy ~/bsd-sharp/lang/mono]$ make prefix=~/_progs DISTDIR=~/_progs/distfiles WRKDIRPREFIX=~/_progs/work INSTALL_AS_USER=1 PREFIX=~/_progs PKG_DBDIR=~/_progs/pkg_db

........

cd ../mcs && gmake NO_DIR_CHECK=1 PROFILES='net_1_1 net_2_0 net_3_5 net_2_1' CC='cc' all-profiles gmake[3]: Entering directory /place/home/xxx/_progs/work/place/home/xxx/bsd- sharp/lang/mono/work/mono-2.4/mcs' gmake profile-do--net_1_1--all profile-do--net_2_0--all profile-do--net_3_5--all profile-do--net_2_1--all gmake[4]: Entering directory/place/home/xxx/_progs/work/place/home/xxx/bsd- sharp/lang/mono/work/mono-2.4/mcs' gmake PROFILE=basic all gmake[5]: Entering directory /place/home/xxx/_progs/work/place/home/xxx/bsd- sharp/lang/mono/work/mono-2.4/mcs' gmake[6]: *** [build/deps/basic-profile-check.exe] Error 1 gmake[6]: Entering directory/place/home/xxx/_progs/work/place/home/xxx/bsd- sharp/lang/mono/work/mono-2.4/mcs' * The compiler 'false' doesn't appear to be usable. Trying the 'monolite' directory. gmake[7]: Entering directory /place/home/xxx/_progs/work/place/home/xxx/bsd- sharp/lang/mono/work/mono-2.4/mcs' gmake[8]: *** [build/deps/basic-profile-check.exe] Error 138 gmake[8]: Entering directory/place/home/xxx/_progs/work/place/home/xxx/bsd- sharp/lang/mono/work/mono-2.4/mcs' The contents of your 'monolite' directory may be out-of-date You may want to try 'make get-monolite-latest' gmake[8]: [do-profile-check-monolite] Error 1 gmake[8]: Leaving directory /place/home/xxx/_progs/work/place/home/xxx/bsd- sharp/lang/mono/work/mono-2.4/mcs' gmake[7]: *** [do-profile-check] Error 2 gmake[7]: Leaving directory/place/home/xxx/_progs/work/place/home/xxx/bsd- sharp/lang/mono/work/mono-2.4/mcs' gmake[6]: [do-profile-check-monolite] Error 2 gmake[6]: Leaving directory /place/home/xxx/_progs/work/place/home/xxx/bsd- sharp/lang/mono/work/mono-2.4/mcs' gmake[5]: *** [do-profile-check] Error 2 gmake[5]: Leaving directory/place/home/xxx/_progs/work/place/home/xxx/bsd- sharp/lang/mono/work/mono-2.4/mcs' gmake[4]: [profile-do--basic--all] Error 2 gmake[4]: Leaving directory /place/home/xxx/_progs/work/place/home/xxx/bsd- sharp/lang/mono/work/mono-2.4/mcs' gmake[3]: *** [profiles-do--all] Error 2 gmake[3]: Leaving directory/place/home/xxx/_progs/work/place/home/xxx/bsd- sharp/lang/mono/work/mono-2.4/mcs' gmake[2]: [all-local] Error 2 gmake[2]: Leaving directory /place/home/xxx/_progs/work/place/home/xxx/bsd- sharp/lang/mono/work/mono-2.4/runtime' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory/place/home/xxx/_progs/work/place/home/xxx/bsd- sharp/lang/mono/work/mono-2.4' gmake: [all] Error 2 * Error code 2

Stop in /place/home/xxx/bsd-sharp/lang/mono.

I'm having the same problem as RealFduch:

* [build/deps/basic-profile-check.exe] Error 138

then the whole process aborts. This is on 6.2-STABLE i386

Now running on 6.4-STABLE and have the same problem.

Which mono version?

Are you running on a real machine or some kind of virtual machine?

Are you compiling with the GENERIC kernel with default compilation knobs as advised in the pkg-message?

Comment deleted

• Mono 2.4.2.2
• Real machine
• Default CFLAGS and CPUTYPE
• Custom kernel, copy of GENERIC with very little changed. SYSVSHM, SYSVMSG and SYSVSEM are in my kernel
• Both my kern.ipc.semmn and kern.ipc.semmns are larger than 40/300 (for other reasons)
• Ensured that I don't have anything using semaphores (deleted what remained with ipcrm)

Older versions of Mono worked just fine, just having a lot of problems with this one.

I have just compiled mono-2.4.2.3 (from BSD# Ports) and trunk from Novell in FreeBSD 8.0-CURRENT amd64 at revision196015 without any problem.

I have run into this problem on my dual-core Turion64 X2 notebook running FreeBSD-CURRENT/amd64.

However, I do not run into the problem on my single-core AthlonXP 2200+ running FreeBSD-CURRENT/i386.

Perhaps the identification of a working and non-working platform might help narrow the problem down.

Oh, and if I issue a 'sudo killall -CONT mono' it will cause mono to get un-stuck and continue execution.

Do you still have this problem ?

Change owner to me

Closing since we have no news about this issue which was opened a long time ago.