From owner-freebsd-current@FreeBSD.ORG Sat Jun 26 03:03:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8C6D16A4CE; Sat, 26 Jun 2004 03:03:54 +0000 (GMT) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C26943D1D; Sat, 26 Jun 2004 03:03:54 +0000 (GMT) (envelope-from johnmary@adelphia.net) Received: from 68-169-191-75.losaca.adelphia.net ([68.169.191.75]) by mta9.adelphia.netESMTP <20040626030326.VSKI23406.mta9.adelphia.net@68-169-191-75.losaca.adelphia.net>; Fri, 25 Jun 2004 23:03:26 -0400 Received: by 68-169-191-75.losaca.adelphia.net (Postfix, from userid 1001) id 66D7F6683; Fri, 25 Jun 2004 20:03:25 -0700 (PDT) Date: Fri, 25 Jun 2004 20:03:25 -0700 From: John Merryweather Cooper To: Joe Marcus Clarke Message-ID: <20040626030325.GB84377@borgdemon.losaca.adelphia.net> References: <20040625204444.GA50921@borgdemon.losaca.adelphia.net> <1088197748.842.1.camel@gyros> <20040626010822.GB20786@borgdemon.losaca.adelphia.net> <1088218523.17696.2.camel@shumai.marcuscom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1088218523.17696.2.camel@shumai.marcuscom.com> User-Agent: Mutt/1.4.2.1i Phone: 1-509-338-9391 WWW-Home-Page: http://www.borgsdemons.com/ cc: freebsd-current@freebsd.org cc: freebsd-gnome@freebsd.org cc: John Merryweather Cooper Subject: Re: Does -CURRENT's gcc generate ___tls_get_addr under any circumstances X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jun 2004 03:03:55 -0000 On Fri, Jun 25, 2004 at 10:55:23PM -0400, Joe Marcus Clarke wrote: > On Fri, 2004-06-25 at 21:08, John Merryweather Cooper wrote: > > On Fri, Jun 25, 2004 at 05:09:08PM -0400, Joe Marcus Clarke wrote: > > > On Fri, 2004-06-25 at 16:44, John Merryweather Cooper wrote: > > > > I'm working on porting (and getting fully working) lang/mono > > > > version 0.96, and I'm having a problem. In one of my object > > > > files--mini.lo--I'm getting an extern reference to > > > > ___tls_get_addr. I've been over the source code in mini.c > > > > and all the included headers, and I can't find anything to > > > > get rid of this reference or find a way to resolve it. As > > > > a result, the linking of the mono runtime binary fails with > > > > this symbol unresolved. > > > > > > > > Any and all clues are welcome! > > > > > > As I recall, this is from boehm. You'll have to tell boehm not to do > > > thread-local storage. Note: boehm is in the libgc subdirectory inside > > > mono. > > > > > > Joe > > > > > > > > > > > jmc > > > > _______________________________________________ > > > > freebsd-gnome@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-gnome > > > > To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.org" > > > -- > > > PGP Key : http://www.marcuscom.com/pgp.asc > > > > > > > > > > Hmmm . . . > > > > Well, looking at the libgc code, I note that if it detects GCC 3.x it uses > > pthreads for thread local storage. The configure script doesn't provide > > a means to turn off tls. > > > > Just to be sure, I undefined USE_COMPILER_TLS on the command line with > > -UUSE_COMPILER_TLS. > > I think you have to remove this from libgc's configure script. You > should be able to do a case statement, and match on freebsd. > > > > > No dice, ___tls_get_addr still shows up in the mini.lo object which gets linked > > into libmono.so which causes mono to fail to link with an undefined > > symbol (see attached build script). > > > > I've checked all the objects in libgc, and none of them are defining > > this symbol. It seems prettly clear that it comes into existance > > during the compile of mini.c (it's in mini.lo), but I can't for the > > life of me find were it is in mini.c or in it's includes. > > I saw this, too, when I was testing an earlier version of mono. I had > actually enabled some additional options thinking they would help, but > it turned out to be a bad idea. > > See if you can hunt down the TLS options in libgc's configure, and > remove them. > > Joe > > > > > jmc > -- > PGP Key : http://www.marcuscom.com/pgp.asc OK, I'll dive into libgc's configure. I can confirm that this is problem reoccurs with 0.97 (which I'm now working on) which has become the release candidate. jmc