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>, 
	bug-followup at freebsd.org
Cc:  
Subject: RE: ports/175518: lang/mono is not configured correctly when building
Date: Mon, 4 Feb 2013 16:05:17 -0500

 Hi Romain,
 
 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.
 
 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.
 
 Regards,
 Jack
 
 -----Original Message-----
 From: Romain Tarti=E8re [mailto:romain at blogreen.org]
 Sent: Monday, February 04, 2013 3:18 PM
 To: bug-followup at FreeBSD.org; jack.pappas at tidepowerd.com
 Subject: Re: ports/175518: lang/mono is not configured correctly when
 building
 
 Hello
 
 I could build lang/mono with just patching the configure script
 (attached) and `mono --gc=3Dsgen` seems ok.
 
 However, you say that mono is not configured correctly without running
 autogen.sh.  Can you please provide more details about what is different
 if you run it and if you directly use configure (assuming both are patched
 to remove 'with_tls=3Dpthread') ?  Or maybe you just wanted to avoid to
 patch this generated 'configure' file ?
 
 We do this because we try to avoit to bring-in all autotools dependencies
 (the port would require adding these extra dependencies to the Makefile
 using:
 
 USE_AUTOTOOLS=3D	libtool:env automake:env autoconf:env aclocal:env
 
 ).
 
 --
 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=
 )