From owner-freebsd-toolchain@FreeBSD.ORG Fri Jul 6 15:10:41 2012 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3A771065675 for ; Fri, 6 Jul 2012 15:10:41 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 70E878FC0A for ; Fri, 6 Jul 2012 15:10:38 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so15821616pbb.13 for ; Fri, 06 Jul 2012 08:10:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=C/Bw7lyf9CRxYvqfXWSVDHtE4yyZkRMRRuyXYtymhk8=; b=D5dSYxcLkCgLL/aWlHvx0XRj8PCS21+N/VqZ4dGgLGb0W4RBxfm42AesTymEtgbdzu kx9kX2FRPEIYECIpKvLKASYTcgN/5r1kdi7Fl6sH0MFWEzT8E8Y8751r6YXsjBQ+KPz4 UfKfB3sS+GWmGBD3LDpUdZkkTYB4k9CoB8YsQc5tjdfuj56qadA53VtqpNyWGFqyAD64 ov7txfHQptHvopdm/bubHzxb0Hz3cNBxJg8vYWzqM0Bx1PbCezTpcsLLET9VKM/8ox79 CBvspeeEdgH4LlVUWMDW0zuo2GVxUdM0WRzFQ1aWPKBSA/wpO8sepv2QT3/ByjfNfC0h fiAg== Received: by 10.68.221.74 with SMTP id qc10mr37309774pbc.31.1341587437843; Fri, 06 Jul 2012 08:10:37 -0700 (PDT) Received: from [10.0.0.63] (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPS id rg9sm22023837pbc.67.2012.07.06.08.10.37 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 06 Jul 2012 08:10:37 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <4FF6DB51.40904@FreeBSD.org> Date: Fri, 6 Jul 2012 09:10:34 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <508B8B4E-DF5E-412B-BD2B-86F21EBF4C8C@bsdimp.com> References: <4FF60A9E.5070503@FreeBSD.org> <4FF6DB51.40904@FreeBSD.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQnGwRfZiMeeSLOq06DWJk4130TkmfXWjAYhDmt22/jvkqaxwub4RlZGVaRPnFGlbl6Sp5lL Cc: toolchain@FreeBSD.org Subject: Re: gcc46 header search path X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jul 2012 15:10:41 -0000 Top posting, because I'm lame... I think it shouldn't be there. It is non-standard behavior both in the = gcc world and in the freebsd world. It does save a little on makefiles = on some ports, but most ports already grok things are in /usr/local or = opt/local and cope. Warner On Jul 6, 2012, at 6:34 AM, Andriy Gapon wrote: >=20 > Inviting wider audience to the discussion. >=20 > -------- Original Message -------- > Date: Fri, 06 Jul 2012 00:43:58 +0300 > From: Andriy Gapon > Subject: Re: gcc46 header search path >=20 > on 05/07/2012 17:15 Andriy Gapon said the following: >>=20 >> Gerald, >>=20 >> while thinking what to reply in our other conversation I ran into = another issue >> with gcc46: >>=20 >> $ echo "" | cpp46 -v >> [trim] >> #include "..." search starts here: >> #include <...> search starts here: >> /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.3/include >> /usr/local/include >> = /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.3/include-fixed >> /usr/include >> End of search list. >> [trim] >>=20 >> I don't think that /usr/local/include should automagically appear in = the search >> list. Base gcc doesn't have it and there doesn't seem to be a good = reason to >> include "arbitrary" non-system directory into the default search = path. >>=20 >=20 > On the other hand the above seems to match the default upstream = behavior as > described here: http://gcc.gnu.org/onlinedocs/cpp/Search-Path.html > It's understandable that such a difference between the base gcc = compiler and gcc > compilers from ports introduces subtle issues to ports. >=20 > I am now confused and torn as to which behavior should be preferable. > On one hand it's easier to patch the port gcc-s to match the base one. > On the other hand the default gcc behavior would save many lines in = port > makefiles that explicitly add -I ${LOCALBASE}/include or some such to = CFLAGS. > buildworld and buildkernel (and etc) could be spared from any = interference from > /usr/local by using -nostdinc and explicitly setting all necessary = include paths. >=20 > Adding more people to conversation in hope that it could become = fruitful. >=20 >=20 > --=20 > Andriy Gapon >=20 >=20 >=20 > _______________________________________________ > freebsd-toolchain@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain > To unsubscribe, send any mail to = "freebsd-toolchain-unsubscribe@freebsd.org"