[Mono-bugs] [Bug 74333][Cri] New - XSP 1.0.6 won't compile

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by ron@rongage.org.

http://bugzilla.ximian.com/show_bug.cgi?id=74333

--- shadow/74333	2005-04-02 12:37:39.000000000 -0500
+++ shadow/74333.tmp.25139	2005-04-02 12:37:39.000000000 -0500
@@ -0,0 +1,78 @@
+Bug#: 74333
+Product: Mono: Tools
+Version: 1.0
+OS: 
+OS Details: Slackware Linux
+Status: NEW   
+Resolution: 
+Severity: Unknown
+Priority: Critical
+Component: XSP
+AssignedTo: gonzalo@ximian.com                            
+ReportedBy: ron@rongage.org               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: XSP 1.0.6 won't compile
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+Doing a fresh build of Mono, mod_mono and XSP on a Slackware system.  Mono
+compiles cleanly as does mod_mono.  XSP refuses to compile at all.  It
+looks like XSP is mistakenly thinking that I have the .NET 2.0 components
+installed and I don't.  This mistake is based on the presence of gmcs
+(installed from mono-1.1.6).  Renaming the installed gmcs to gmcs.hold
+causes the configure script for XSP correctly say no 2.0 components, but
+the build system then tries to build the 2.0 server using the executable
+called "no".  Obviously, this doesn't work.
+
+The correct first fix here is to use some method other than the presence of
+gmcs to determine if .NET 2.0 is supported or not.  The second fix should
+be trivial - if the compiler is set to 'no', don't try to run it!  :)
+
+
+Obligatory output dump follows:
+
+root@raid:~/apache/mono/xsp-1.0.6# make
+Making all in man
+make[1]: Entering directory `/root/apache/mono/xsp-1.0.6/man'
+cp xsp.1 mod-mono-server.1
+make[1]: Leaving directory `/root/apache/mono/xsp-1.0.6/man'
+Making all in server
+make[1]: Entering directory `/root/apache/mono/xsp-1.0.6/server'
+/usr/local/bin/mcs -debug+ -debug:full -nologo -r:System.Web.dll
+-r:Mono.Posix.dll /d:MODMONO_SERVER /out:mod-mono-server.exe
+./IApplicationHost.cs ./MonoWorkerRequest.cs ./Tracing.cs
+./ApplicationServer.cs ./LingeringNetworkStream.cs ./BaseApplicationHost.cs
+./BaseRequestBroker.cs ./IWebSource.cs ./server.cs ./ModMonoRequest.cs
+./ModMonoWorkerRequest.cs ./ModMonoApplicationHost.cs
+./ModMonoTCPWebSource.cs AssemblyInfoModMono.cs
+no -debug+ -debug:full -nologo -r:System.Web.dll -r:Mono.Posix.dll
+/d:MODMONO_SERVER /out:mod-mono-server2.exe ./IApplicationHost.cs
+./MonoWorkerRequest.cs ./Tracing.cs ./ApplicationServer.cs
+./LingeringNetworkStream.cs ./BaseApplicationHost.cs ./BaseRequestBroker.cs
+./IWebSource.cs ./server.cs ./ModMonoRequest.cs ./ModMonoWorkerRequest.cs
+./ModMonoApplicationHost.cs ./ModMonoTCPWebSource.cs AssemblyInfoModMono.cs
+make[1]: no: Command not found
+make[1]: *** [mod-mono-server2.exe] Error 127
+make[1]: Leaving directory `/root/apache/mono/xsp-1.0.6/server'
+make: *** [all-recursive] Error 1
+
+
+Steps to reproduce the problem:
+1. ./configure
+2. make
+3. 
+
+Actual Results:
+See above
+
+Expected Results:
+Production of .NET 1.1 compatible server app.
+
+How often does this happen? 
+100% consistent
+
+Additional Information: