From owner-freebsd-ports Tue Jun 1 20:48:20 1999 Delivered-To: freebsd-ports@freebsd.org Received: from shell13.ba.best.com (shell13.ba.best.com [206.184.139.144]) by hub.freebsd.org (Postfix) with ESMTP id 6E20614E22 for ; Tue, 1 Jun 1999 20:48:18 -0700 (PDT) (envelope-from rone@ennui.org) Received: (from rone@localhost) by shell13.ba.best.com (8.9.3/8.9.2/best.sh) id UAA01081 for ports@freebsd.org; Tue, 1 Jun 1999 20:48:11 -0700 (PDT) From: "gil i. pollas" Message-Id: <199906020348.UAA01081@shell13.ba.best.com> Subject: Re: Making egcs the default for building ports In-Reply-To: from Chuck Robey at "Jun 1, 99 11:21:42 pm" To: ports@freebsd.org Date: Tue, 1 Jun 1999 20:48:11 -0700 (PDT) X-URL: http://ennui.org/rone/ X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Chuck Robey writes: On Tue, 1 Jun 1999, gil i. pollas wrote: > Chuck Robey writes: > On Tue, 1 Jun 1999, J. Heinrich wrote: > > On Mon, May 31, 1999 at 04:01:26PM -0400, Chuck Robey wrote: > > > Most often, you can do: > > > setenv CC (path to your egcs compiler) > > > setenv CXX (path to your egcs C++ compiler) > > But I'd have to remember to do this every time. > certainly not. Either stick it in your .cshrc (or the equivalent > startup file for your chosen shell) or (far better) make a shell script > that changes your PATH variable, or resets your path variable back > again. > Unfortunately, that carries over when you want to build a kernel or > world. Most of us probably don't want that. No it does not, you didn't read the whole paragraph. You make a shell script the changes it, and invoke the shell script to run your port compile. You then either source your shell startup file to reset your path, or if your shell startup isn't idempotent, then make another short shell script to reset your path, use it and then do your kernel build. That's cheesy. You might as well just setenv CC before you do a port build and unsetenv it when you're done. A SYSCC environment variable that applies to FreeBSD source would leave CC free for ports and other non-system compilations. The real question is, would this move have any drawbacks (or is it superfluous or pointless)? rone -- el mercado on the corner has grande bags of clues rilly cheapo. - Patrick J. Finerty To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message