From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 00:42:37 2012 Return-Path: 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 BA0C6BB1; Sat, 13 Oct 2012 00:42:37 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-da0-f54.google.com (mail-da0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7ED568FC08; Sat, 13 Oct 2012 00:42:37 +0000 (UTC) Received: by mail-da0-f54.google.com with SMTP id z9so1693316dad.13 for ; Fri, 12 Oct 2012 17:42:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=w2/ID+DAGkhhTPRCQVbOnnbEewWDw5+DRmngM32bqRE=; b=L3CyYAaR6/9IMoWcV+KrRh64F62DsfXscJ2+JjsSHh1kbwZ64O7PeazGp0I0pYyVK4 p0oQhUkVhO/Vpbqus7Thjf1MedKDwNqh65ymox3D1Py6FXbvRQ+3Uwdx4wv20+Cot9Gc nui0iK2lNOF2iwIFpPB0S+nD2lzJxmnbNlhdpHBTtmLUbWrgZzEZs6gyr9Ls8sIjhPan RHTLk4bCqUap4zvK5eNFmvL+NQFdwfWY+ngPILE6AOiSsU/7RDcZu+GV003IKtXVOuQe e6xUtRr/TrO3xPPKmbJLJs8dXuEJd2Mzon1RKQjIgu5FHuXBy9vXMsQE7+rJBryW79xW fouw== Received: by 10.68.222.228 with SMTP id qp4mr18016113pbc.96.1350088956923; Fri, 12 Oct 2012 17:42:36 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id ru4sm5190081pbc.25.2012.10.12.17.42.33 (version=SSLv3 cipher=OTHER); Fri, 12 Oct 2012 17:42:35 -0700 (PDT) Message-ID: <5078B8EA.9080207@gmail.com> Date: Fri, 12 Oct 2012 17:42:18 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: Claude Buisson Subject: Re: [HEADSUP] FYI: patch to ports that do not build with clang has been committed References: <20121010004523.GA15209@lonesome.com> <5075365C.4050400@orange.fr> <507787CF.1090705@gmail.com> <5077CC99.4010104@orange.fr> In-Reply-To: <5077CC99.4010104@orange.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mark Linimon , freebsd-current@FreeBSD.org, freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Sat, 13 Oct 2012 00:42:37 -0000 On 10/12/12 00:54, Claude Buisson wrote: > On 10/12/2012 05:00, matt wrote: >> >>>> >>>> I have made changes to ports/Mk/bsd.gcc.mk that allow the addition of >>>> "USE_GCC=any" to a port's Makefile, and then committed that change to >>>> various ports. In most (but not all!) cases this will tell the port >>>> "build with gcc instead of clang" (*) . >>>> >>> >>> Why not USE_GCC ?= any for the poor guys like me who build (some) >>> ports with >>> USE_GCC=4.6 ? >>> >>>> For those users with CC installed as gcc (including -stable), this >>>> patch should have no effect. Variations of combinations have been >>>> heavily tested on pointyhat-west. If there are any regressions, >>>> please >>>> contact me. >>>> >>> >>> >> >> Does this override setting CC explicitly in make.conf? >> Sorry if it's a dumb question, not sure exactly the hierarchy of USE_GCC >> vs CC in the make system. >> > > Dumb as I am, I also wonder when I see that in multimedia/x264: > > ... > USE_GCC= any > ... > .if ${PORT_OPTIONS:MGCC44} > USE_GCC?= 4.4+ > .endif > ... > > which seems to deny the intent of the GCC44 option > > Sorry but I can not make the test at this present time > >> Matt > > Claude Buisson > I tested, and can confirm two things. CC is overpowered by USE_GCC=any, which means that I end up with no sse4a and limited support for my arch (Opteron 4xxx) because I can't set a better -march/cputype than opteron-sse3. As far as I know base gcc doesn't even support sse4a. This is really perhaps an issue with me setting CC in make.conf moreso than ports, however this was the approved method of using clang by default as well as the approved method of using ports gcc in the ports system. Is there a new approved method? M. Buisson's test case also fails, with base gcc being used even though the gcc44 option is chosen. This may not break as many ports as it might, but it will certainly create low performing editions of many multimedia ports given the CPU features supported by either later clang or gcc. Some will probably break? If I missed something, please let me know, or if my testing is somehow compromised. I removed make.conf (as mine is customized) for Claude's test case, but it's possible something else may have affected my test results. USE_GCC=any was manually added to the ports makefiles (test case was editors/nano and multimedia/x264). Matt