ports/69848: lang/mono functions properly on 5.x if ${PREFIX}/bin/mono is in libmap.conf

[Christopher Nehren]

>Number:         69848
>Category:       ports
>Synopsis:       lang/mono functions properly on 5.x if ${PREFIX}/bin/mono is in libmap.conf
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jul 31 15:20:23 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Christopher Nehren
>Release:        FreeBSD 5.2.1-RELEASE-p8 i386
>Organization:
>Environment:
System: FreeBSD prophecy.dyndns.org 5.2.1-RELEASE-p8 FreeBSD 5.2.1-RELEASE-p8 #0: Sun Jun 6 16:04:08 EDT 2004 root at prophecy.dyndns.org:/usr/obj/usr/src/sys/PROPHECY i386


	
>Description:
I noticed that mono had a maintainer, and that it was marked as broken for
all 5.x versions of FreeBSD below 502113. I went looking through cvsweb and
didn't see anything committed between 502113 and 502010 which would somehow make
Mono work. I removed the relevant lines from lang/mono/Makefile, built it, ran 
it, and had no problems. I wanted to make sure that everything was all right, 
so I decided to build something to exercise the program: gtk-sharp. It paused 
at part of the build, but placing ${PREFIX}/bin/mono in libmap.conf has fixed 
this. I can now run the samples in the gtk-sharp distribution without any 
problems.
>How-To-Repeat:
1. Build mono.
2. Attempt to build x11-toolkits/gtk-sharp.
3. Notice the CPU hogging of a runaway mono process.
4. Place ${PREFIX}/bin/mono in libmap.conf.
5. Reattempt the x11-toolkits/gtk-sharp build.
6. Succeed with step 5.
7. Test the samples.
>Fix:
Remove the relevant lines from lang/mono/Makefile and create a pkg-message
stating the required change for it to work on 5.x releases < 502113.
>Release-Note:
>Audit-Trail:
>Unformatted: