[Mono-bugs] [Bug 50654][Nor] New - mono-build-w32.sh not compatible with cygwin

[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 miguel@ximian.com.

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

--- shadow/50654	2004-05-13 15:24:17.000000000 -0400
+++ shadow/50654.tmp.28431	2004-05-13 15:24:17.000000000 -0400
@@ -0,0 +1,102 @@
+Bug#: 50654
+Product: Mono: Runtime
+Version: unspecified
+OS: unknown
+OS Details: Windows 2000 all service packs + cygwin
+Status: NEW   
+Resolution: 
+Severity: 040 One week
+Priority: Normal
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: fgenolini@hotmail.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: mono-build-w32.sh not compatible with cygwin
+
+Please fill in this template when reporting a bug, unless you know what 
+you are doing.
+Description of Problem:
+mono-build-w32.sh not compatible with cygwin
+
+Steps to reproduce the problem:
+1. install from fresh OS, .Net SDK and cygwin (6th Nov 2003)
+2. download mono-build-w32.sh from http://www.go-mono.org/mono-build-w32.sh
+3. run it as documented in
+http://www.go-mono.com:8080/
+Mono Documentation
+Mono Handbook
+PART 2 - Installing Mono and Choosing the IDE
+Chapter 3 - Getting Started
+Installation on Windows
+http://www.go-mono.com:8080/monodoc.ashx?tlink=5@xhtml%3Ahtml%2Fen%
+2Finstallation%2Fwindows.html
+Building Mono under Windows
+
+Actual Results:
+Breaks in great many places, mainly because the configure.in of libgc and 
+others rely on an old autoconf (2.53) where now cygwin uses 2.57
+
+Expected Results:
+Mono should build as documented and script file should always cope with 
+latest full cygwin install
+
+How often does this happen? 
+
+
+Additional Information:
+
+The page for the "OS Details" link on
+http://bugzilla.ximian.com/bug_status.html#op_sys_details
+does not exist
+
+------- Additional Comments From fgenolini@hotmail.com  2003-11-06 12:36 -------
+If you go to /usr/autotool rename stable into foo and then create a 
+soft link from devel to stable, this causes autconf to use 
+the "devel" version.
+
+This bug was first pointed out by Bug 48049
+
+
+------- Additional Comments From kwhite65@mindspring.com  2003-11-22 12:20 -------
+Items needed to make Mono on XP...
+
+Cygwin:
+
+Be sure to have the default cygwin installed.  Make sure that when 
+you set a user up, there are no spaces in the name. Bad redhat 
+engineer who allows a space in input for user name when it breaks 
+things horribly later.  In addition, make sure the following 
+packages are installed as well:
+perl(interpreters), wget(web), libtool(devel), unzip (), libiconv
+(devel), gcc (devel), lots of hidden gcc components must be 
+installed too.  I am not sure how I got as far as I did now...
+
+Copy /bin/aclocal-1.7 to aclocal-1.4 (this does not exist)
+Copy /bin/automake-1.4 to automake-1.4 (this does not exist either)
+
+Copy CC1.exe into /bin (not sure why this didn't copy into a bin 
+directory through the install)
+
+Be sure to let people know about the config.log in the /home/mono 
+directory, because with this many dependancies (i.e. - cygwin), it 
+will most assuredly will not work.
+
+Script in home directory doesn't work, because autoconf has a 
+wrapper which returns a different value for --version than the 
+actual autoconf program does.  This wrapper returns a different 
+value when in the mono directory, and is less than the acceptable 
+value, which in-turn produces a FATAL ERROR.
+
+Remove -V option from gcc as it causes the compiler to break, the -V 
+option must be first in line, not last.  Best results are with this 
+removed altogether.  Make sure configure.in in the home/user/mono 
+directory as well as /mono/configure are changed.  Very annoying to 
+copy over these files every time the script is run.
+
+cannot open crtbegin.o: No such file or directory -- caused because 
+mingw has been chosen rather than cygwin -- the compiler is looking 
+in .../i686-pc-mingw32, rather than ../i686-pc-cygwin, where the 
+file really is...