Bug 32000 - Confusion about --with-gc
Summary: Confusion about --with-gc
Status: NEW
Alias: None
Product: Runtime
Classification: Mono
Component: General ()
Version: 4.0.0
Hardware: PC Other
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-07-16 05:08 UTC by Rainer Orth
Modified: 2015-07-16 05:09 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

pro (1.14 KB, patch)
2015-07-16 05:09 UTC, Rainer Orth

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 32000 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Rainer Orth 2015-07-16 05:08:28 UTC
When trying to build mono on 64-bit Solaris 11/x86 (x86_64-pc-solaris2.11), I ran into the fact that the
bundled version of libgc doesn't include 64-bit Solaris/x86 support.  I'd run into this problem already with
mono 3.2.6, and had good success with upstream libgc 7.2, so I meant to try this again.  Unfortunately, this failed
since the --with-gc=boehm configure option was ignored; I had to resort to moving libgc in the source tree aside.

On closer inspection, I found that there's lots of confusion in configure.ac's handling of that option:

While configure.ac checks for a --with-libgc option, the option's help message still refers to --with-gc which
doesn't exist any longer.  Even so, the code to handle --with-libgc only checks a with_gc variable which is only
set in two exceptional cases.

The attached patch fixes those issues, correcting the help message and consistently using with_libgc.

Comment 1 Rainer Orth 2015-07-16 05:09:07 UTC
Created attachment 12056 [details]