From owner-freebsd-current@FreeBSD.ORG Mon Jun 4 00:23:38 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 444A716A481; Mon, 4 Jun 2007 00:23:38 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.freebsd.org (Postfix) with ESMTP id 247FA13C4B8; Mon, 4 Jun 2007 00:23:38 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from hymn03.u.washington.edu (hymn03.u.washington.edu [140.142.12.169]) by mxout7.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.05) with ESMTP id l540Nbqg012652 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 3 Jun 2007 17:23:37 -0700 Received: from localhost (localhost [127.0.0.1]) by hymn03.u.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l540NbXK015379; Sun, 3 Jun 2007 17:23:37 -0700 X-Auth-Received: from [134.134.136.3] by hymn03.u.washington.edu via HTTP; Sun, 03 Jun 2007 17:23:37 PDT Date: Sun, 3 Jun 2007 17:23:37 -0700 (PDT) From: youshi10@u.washington.edu To: Doug Barton In-Reply-To: <46634D28.8060503@u.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.6.3.170236 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: current@freebsd.org Subject: Re: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 04 Jun 2007 00:23:38 -0000 On Sun, 3 Jun 2007, Garrett Cooper wrote: > Doug Barton wrote: >> Garrett Cooper wrote: >> >>> Is there a reason why this line of code is invalid for amd64 (from >>> /usr/src/contrib/bind9/lib/isc/x86_64/include/isc/atomic.h:25-28)? >>> >>> #ifdef ISC_PLATFORM_USEGCCASM >>> >>> /* We share the gcc-version with x86_32 */ >>> #error "impossible case. check build configuration" >>> >>> After doing some searching, all that that macro does is use says the >>> OS can use gcc asm instructions. >>> >> >> Yeah, I looked at that header and asked myself the same question. I'm >> going to follow up with the ISC folks on that issue. >> >> Meanwhile I finally got access to an amd64 machine that I could build >> the port on (our reference system is literally FUBAR), and it looks >> like things are in better shape than I feared. Ruslan's suggestion of >> using the x86_32 atomic.h header that I already committed turns out to >> be how the port does it, and the other generated headers look good, so >> the build should be fine now. If anyone could confirm that with >> sources that include v. 1.18 of src/lib/bind/config.mk the world >> actually builds, I'd appreciate it. If you could do some rudimentary >> testing of the results, I'd be eternally grateful. :) >> >> FWIW, I relied on the fact that the bind94 port builds just fine on >> our platforms to convince me that things would be fine for the base. >> While that seems to have worked for most of the cases, it turns out to >> have not been a good assumption to make. I apologize for the >> inconvenience that I created. >> >> >> Mea culpa, >> >> Doug > Ok, I'll give it a shot now Doug. > > Thanks! > -Garrett buildworld just passed the bind9 section on my EMT64 machine, so I think it's safe to say that bind9's in the clear now :). -Garrett