From owner-freebsd-current@FreeBSD.ORG Mon Apr 28 15:52:47 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BE0C9369; Mon, 28 Apr 2014 15:52:47 +0000 (UTC) Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 82FF21DE8; Mon, 28 Apr 2014 15:52:47 +0000 (UTC) Received: by mail-pd0-f180.google.com with SMTP id x10so2484036pdj.11 for ; Mon, 28 Apr 2014 08:52:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=V+0DE/87ZACIrBAuwqbT8S3RP8EKSiWBBo9Wpc+jDz0=; b=0uZ+Zg7yr03qC7KnHfh3fMIUp6pgWaK8R7mLA1tHUguBhHakt3BrQc00vXAXZTD6r6 UhASftersqUyIkPWkpuh05waCFu9qFKrtP3LjQ/xS7uuXtIwBFkRb0zodXH6mz1fPwsZ XsMvniOHOSIAZdhnse8UiGFzLbUoABAPoIJwPQeRkyJ07pOkVYIyy7R06UDpl/qqkCm2 Li8oYyKrsccSy2MBytBrGu2Ftlx2NtA5WSXqegjz2cAD0eteAYBgM4XD8HiQly5WdsnN WB0ZWk7QCaA4/2psJFztWKdfmutsXzUOyA2wEnKJkAX+nmgi/y/xmpgGGPC/t8ilR38x HMsQ== MIME-Version: 1.0 X-Received: by 10.68.226.35 with SMTP id rp3mr26369136pbc.73.1398700367080; Mon, 28 Apr 2014 08:52:47 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.66.73.34 with HTTP; Mon, 28 Apr 2014 08:52:46 -0700 (PDT) In-Reply-To: <1398695014.61646.212.camel@revolution.hippie.lan> References: <535D1350.4000106@freebsd.org> <1398616234.61646.155.camel@revolution.hippie.lan> <535DFB11.4020904@freebsd.org> <1398686749.61646.203.camel@revolution.hippie.lan> <535E5FA0.9050703@freebsd.org> <1398695014.61646.212.camel@revolution.hippie.lan> Date: Mon, 28 Apr 2014 08:52:46 -0700 X-Google-Sender-Auth: ifBnO8waI5grLHmG9QBaU2iDylo Message-ID: Subject: Re: options for forcing use of GCC From: Kevin Oberman To: Ian Lepore Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Mon, 28 Apr 2014 15:52:47 -0000 On Mon, Apr 28, 2014 at 7:23 AM, Ian Lepore wrote: > On Mon, 2014-04-28 at 22:03 +0800, Julian Elischer wrote: > > On 4/28/14, 8:05 PM, Ian Lepore wrote: > > > On Mon, 2014-04-28 at 14:54 +0800, Julian Elischer wrote: > > >> On 4/28/14, 12:30 AM, Ian Lepore wrote: > > >>> WITH_GCC=yes \ > > >>> WITH_GNUCXX=yes \ > > >>> WITHOUT_CLANG=yes \ > > >>> WITHOUT_CLANG_IS_CC=yes \ > > >> forgot to ask.. is this in /etc/make.conf? > > >> or elsewhere? > > > Actually in our build system we build in a chroot, and we inject those > > > args into the environment during the builds so that we can have > > > different options for building world versus cross-world within the > > > chroot, but I think the more-normal place would be make.conf. > > > > we also use a combination of environment and make.conf in a chroot. > > though people sometimes talk about a src.conf (or is that src.mk?) but > > I haven't found that one yet. > > > > > > -- Ian > > > > > > > > > > > In theory, /etc/make.conf affects all builds you do -- world, kernel, > ports, your own apps, everything -- whereas /etc/src.conf affects only > kernel and world. I've heard it said that the reality falls short of > that and src.conf settings inappropriately leak into ports builds. > > -- Ian > I have also heard this, but a grep of ports/Mk finds no matches to src\.conf, so this appears to not be the case. It should not be as the whole purpose of src.conf was to have a make configuration that would be used to build the system, but not other things. make.conf already provided for that. The only exception I might see is the building of a kernel module which might need to know how the system was made and that would be in the specific port's Makefile, not a system wide file. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com