From owner-freebsd-current@FreeBSD.ORG Thu Jul 8 22:58:40 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 8A85716A4CE for ; Thu, 8 Jul 2004 22:58:40 +0000 (GMT) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 492F643D1F for ; Thu, 8 Jul 2004 22:58:40 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (adsl-67-119-53-245.dsl.lsan03.pacbell.net [67.119.53.245]) i68MwrX9026216; Thu, 8 Jul 2004 18:58:53 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BC9E051386; Thu, 8 Jul 2004 15:58:38 -0700 (PDT) Date: Thu, 8 Jul 2004 15:58:38 -0700 From: Kris Kennaway To: firenze_cena@madpilot.net Message-ID: <20040708225838.GA21617@xor.obsecurity.org> References: <20040707224458.92995.qmail@web40302.mail.yahoo.com> <20040708180046.GA16307@wedge.madpilot.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline In-Reply-To: <20040708180046.GA16307@wedge.madpilot.net> User-Agent: Mutt/1.4.2.1i cc: Maksim Yevmenkin cc: current@freebsd.org Subject: Re: [HEADSUP] bluetooth is about to be marked as non-i386 specific 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: Thu, 08 Jul 2004 22:58:40 -0000 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 08, 2004 at 08:00:46PM +0200, Guido Falsi wrote: > On Wed, Jul 07, 2004 at 03:44:58PM -0700, Maksim Yevmenkin wrote: > > Dear Hackers, > >=20 > > in a few minutes i will be committing small changes to a few Makefile's. > > these changes will take bluetooth code from ".if ${MACHINE_ARCH} =3D=3D > > "i386"" section. i did crossbuild on sledge for the tier 1 platforms > > (amd64, sparc64) and some of the tier 2 platforms (alpha) and it > > worked for me. > >=20 > > i will monitor tinderbox build emails, but if your build failed and > > you believe that it is bluetooth related please let me know right > > away. please note that it is possible to use NO_BLUETOOTH knob to > > disable bluetooth build all together. >=20 > Then you could also remove the ONLY_FOR_ARCHS=3D i386 flag from the > comms/obexapp or should I file a PR checking explicitly for the system > version? (how do I recognize versions prior to this change? :). Maksim should bump __FreeBSD_version so you and the other bluetooth users on !i386 can test for the condition (via OSVERSION in ports) Kris --FCuugMFkClbJLl1L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA7dGeWry0BWjoQKURAiNBAKCa0XnZeNEtCpF4i2sS0O3czxLVFwCg23wQ 0qIopOpqpdwZ1DPXS75EKjE= =2wjv -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L--