From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 6 07:00:21 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 268171065688; Wed, 6 Jul 2011 07:00:21 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9592C8FC16; Wed, 6 Jul 2011 07:00:17 +0000 (UTC) Received: by vxg33 with SMTP id 33so6470742vxg.13 for ; Wed, 06 Jul 2011 00:00:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=N0dCrmE1IU05Rtto7P7ocE09S9qj8W6bmpSZMLJz9eo=; b=LzmFt1mvm0VqXYB95jhn8NzZ1pKrpG/n3pES4gIybcMn/poE3AWOQtfbGSSa2E1+np KJL6RFZeyoSg4lO2SA6KSOA6F4u+OXPzqhs9KyMHwIo13RKCKh0xcJeFQ30Hb9c4aFG6 sdnTDdHKtwc91VcR5p0M0KYHGLHmZ0qqNX//A= MIME-Version: 1.0 Received: by 10.220.59.193 with SMTP id m1mr2275677vch.38.1309935616775; Wed, 06 Jul 2011 00:00:16 -0700 (PDT) Received: by 10.220.92.201 with HTTP; Wed, 6 Jul 2011 00:00:16 -0700 (PDT) In-Reply-To: References: <20110702193724.5c55a6c9@kan.dnsalias.net> <20110703020827.GA5763@sandvine.com> <20110703103531.4a553271@kan.dnsalias.net> <20110705140527.17362ed5@kan.dnsalias.net> <20110705201214.GA31647@sandvine.com> Date: Wed, 6 Jul 2011 00:00:16 -0700 Message-ID: From: Garrett Cooper To: Robert Millan Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, Ed Maste Subject: Re: [PATCH] __FreeBSD_kernel__ X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2011 07:00:21 -0000 On Tue, Jul 5, 2011 at 11:53 PM, Robert Millan wrote: > 2011/7/5 Ed Maste : >> On the topic of where such a macro should be defined I originally had >> no strong opinion. =A0However, valid points have been raised about >> compiling software for FreeBSD using compilers that are not the one in >> the base system (from ports or otherwise, and GCC or otherwise). =A0This >> I think is a very valid point and one that would make me lean towards >> defining the macro in sys/param.h. =A0How workable is it to #include >> sys/param.h to pick up the macro where needed? > > That works most of the time. =A0There could be a problem if software > can't assume is present, but I think it covers the vast > majority of cases. Speaking from my limited experience trying to fix net-snmp's autoconf tests over the past couple of days and maintaining LTP, as well as development in general on FreeBSD and Linux platforms, I think that more of an issue lays in socializing the development structure of FreeBSD to third-parties, in particular because a number of groups fail to adhere to some of the practices that have been explicitly or implicitly put forth by FreeBSD in terms of headers and definitions. Granted, this is one piece of the puzzle, but it's an important one, because the following (for example): $ cat foo.c #include #include #include #include #include ... isn't guaranteed to work :). Thanks, -Garrett