Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 4 Feb 2013 21:50:01 GMT
From:      Romain =?iso-8859-1?Q?Tarti=E8re?= <>
Subject:   Re: ports/175518: lang/mono is not configured correctly when building
Message-ID:  <>

Next in thread | Raw E-Mail | Index | Archive | Help
The following reply was made to PR ports/175518; it has been noted by GNATS.

From: Romain =?iso-8859-1?Q?Tarti=E8re?= <>
To: Jack Pappas <>
Subject: Re: ports/175518: lang/mono is not configured correctly when building
Date: Mon, 4 Feb 2013 22:46:09 +0100

 Content-Type: text/plain; charset=iso-8859-1
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 On Mon, Feb 04, 2013 at 04:05:17PM -0500, Jack Pappas wrote:
 > According to the Mono README
 > (, the 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 was because after I'd
 > patched the 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 that
 > Mono compiled successfully and used the __thread TLS.
 The 'configure' script is generated by the autotools from the
 '' file.  So modifying the '' file require you
 to run all the autotools chain to regenerate the 'configure' script
 before continuing.  This is the reason you had to run ''.
 When the mono folks release a new mono tarball, they include the generated
 'configure' script in it so we have to either patch '' and re-r=
 the whole autotools chain, or patch the generated 'configure' which avoids =
 all the mess that commes with the autotools if we have to change something
 > 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=
 	TLS:           __thread
 	SIGSEGV:       normal
 	Notification:  kqueue
 	Architecture:  amd64
 	Disabled:      none
 	Misc:          softdebug=20
 	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
 Romain Tarti=E8re <>
 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)
 Content-Type: application/pgp-signature
 Version: GnuPG v2.0.19 (FreeBSD)

Want to link to this message? Use this URL: <>