ports/175518: lang/mono is not configured correctly when building

[Jack Pappas]

The following reply was made to PR ports/175518; it has been noted by GNATS.

From: Jack Pappas <jack.pappas at tidepowerd.com>
To: =?ISO-8859-1?Q?Romain_Tarti=E8re?= <romain at blogreen.org>
Cc: bug-followup at freebsd.org
Subject: RE: ports/175518: lang/mono is not configured correctly when building
Date: Mon, 4 Feb 2013 16:55:19 -0500

 HI Romain,
 
 Yes, that's the output I was expecting, so you can commit the change
 whenever you're ready. Thank you for the explanation about the 'configure'
 script -- it does make a lot of sense for Mono to package the sources like
 that now that you mention it.
 
 Regards,
 Jack
 
 -----Original Message-----
 From: Romain Tarti=E8re [mailto:romain at blogreen.org]
 Sent: Monday, February 04, 2013 4:46 PM
 To: Jack Pappas
 Cc: bug-followup at freebsd.org
 Subject: Re: ports/175518: lang/mono is not configured correctly when
 building
 
 On Mon, Feb 04, 2013 at 04:05:17PM -0500, Jack Pappas wrote:
 > According to the Mono README
 > (https://github.com/mono/mono/blob/master/README), the autogen.sh is
 > only needed when building from a snapshot; for official tarballs (like
 > the one used in the lang/mono port), it's not.
 >
 > However, the reason I wanted to use autogen.sh was because after I'd
 > patched the configure.in file (and added the patch to the 'files'
 > directory), I found that when I ran "make install clean", the patch
 > wouldn't work -- Mono would still compile correctly, but it would
 > still use the pthread API for thread-local storage (TLS) instead of
 > the __thread qualifier. It was only after changing the makefile to
 > call autogen.sh that Mono compiled successfully and used the __thread
 TLS.
 
 The 'configure' script is generated by the autotools from the
 'configure.in' file.  So modifying the 'configure.in' file require you to
 run all the autotools chain to regenerate the 'configure' script before
 continuing.  This is the reason you had to run 'autogen.sh'.
 
 When the mono folks release a new mono tarball, they include the generated
 'configure' script in it so we have to either patch 'configure.in' and
 re-run the whole autotools chain, or patch the generated 'configure' which
 avoids us all the mess that commes with the autotools if we have to change
 something there.
 
 > You said you were able to build lang/mono by just patching the
 > configure script -- did you also install it after building? If so, you
 > can run "mono -V" to see what kind of thread-local storage Mono was
 > compiled with. If your installation of Mono is using the __thread TLS,
 > then let's use your method of patching just the 'configure' file.
 
 I get:
 
  JIT compiler version 3.0.3 (tarball Mon Feb  4 14:30:00 CET 2013)
 Copyright (C) 2002-2012 Novell, Inc, Xamarin Inc and Contributors.
 www.mono-project.com
 	TLS:           __thread
 	SIGSEGV:       normal
 	Notification:  kqueue
 	Architecture:  amd64
 	Disabled:      none
 	Misc:          softdebug
 	LLVM:          supported, not enabled.
 	GC:            Included Boehm (with typed GC and Parallel Mark)
 
 which is what you are expecting, right ?  Then I guess I can commit this
 change.
 
 Romain
 
 --
 Romain Tarti=E8re <romain at blogreen.org>        http://romain.blogreen.org/
 pgp: 8234 9A78 E7C0 B807 0B59  80FF BA4D 1D95 5112 336F (ID: 0x5112336F)
 (plain text =3Dnon-HTML=3D PGP/GPG encrypted/signed e-mail much appreciated=
 )