From owner-freebsd-current@FreeBSD.ORG Sun Jun 3 22:20:49 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 C85AD16A468 for ; Sun, 3 Jun 2007 22:20:49 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id 749F813C44C for ; Sun, 3 Jun 2007 22:20:49 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 23921 invoked by uid 399); 3 Jun 2007 22:20:48 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 3 Jun 2007 22:20:48 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <46633EBF.4080209@FreeBSD.org> Date: Sun, 03 Jun 2007 15:20:47 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.0 (X11/20070525) MIME-Version: 1.0 To: Garrett Cooper References: <20070603170828.E45BB73068@freebsd-current.sentex.ca> <4662FFA5.4000602@u.washington.edu> In-Reply-To: <4662FFA5.4000602@u.washington.edu> X-Enigmail-Version: 0.95.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: amd64@freebsd.org, FreeBSD Tinderbox , 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: Sun, 03 Jun 2007 22:20:49 -0000 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 -- This .signature sanitized for your protection