Bug 312080 (MONO39187) - mono-build-w32.sh fails to build a fresh MONO runtime
Summary: mono-build-w32.sh fails to build a fresh MONO runtime
Status: RESOLVED MOVED
Alias: MONO39187
Product: Mono: Runtime
Classification: Mono
Component: misc (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Enhancement
Target Milestone: ---
Assignee: Mono Bugs
QA Contact: Mono Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-06 13:41 UTC by Mitko Iliev
Modified: 2007-09-15 21:24 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Wiest 2007-09-15 18:07:29 UTC


---- Reported by imitko@openlinksw.co.uk 2003-03-06 06:41:02 MST ----

Description of Problem: Not sure for right component ; 
Using the mono-build-w32.sh from web , i have tried to build a fresh 
mono runtime under Windows/Cygwin . So the build fails repeatably with 
'libgc found but not its header files'. Looking at c:\mono\install\include
, there is a gc.h files .... 


Steps to reproduce the problem:
1. get a mono-build-w32.sh from www.go-mono.com
2. start it under cygwin bash in clean c:\mono directory 


Actual Results:
error on configure : 'libgc found but not its header files'

Expected Results:
to compile fresh mono

How often does this happen? 
always

Additional Information:



---- Additional Comments From lupus@ximian.com 2003-04-27 07:47:42 MST ----

*** https://bugzilla.novell.com/show_bug.cgi?id=MONO41352 has been marked as a duplicate of this bug. ***



---- Additional Comments From lupus@ximian.com 2003-04-27 07:49:12 MST ----



*** This bug has been marked as a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=MONO38655 ***


Unknown bug field "cf_op_sys_details" encountered while moving bug
   <cf_op_sys_details>Windows XP</cf_op_sys_details>
Unknown operating system other. Setting to default OS "Other".
This bug was marked DUPLICATE in the database it was moved from.
    Changing resolution to "MOVED"