Date: Tue, 1 Jun 1999 23:57:03 -0400 (EDT) From: Chuck Robey <chuckr@picnic.mat.net> To: "gil i. pollas" <rone@ennui.org> Cc: ports@FreeBSD.ORG Subject: Re: Making egcs the default for building ports Message-ID: <Pine.BSF.4.10.9906012354240.82061-100000@picnic.mat.net> In-Reply-To: <199906020348.UAA01081@shell13.ba.best.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 1 Jun 1999, gil i. pollas wrote: > 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)? Except that you don't have any control over what people use as the CC and CXX vars. FreeBSD isn't going to do that for you, and everyone else in the world won't either. It works, it's what many people use. If you think it's cheesy, come up with a better one. You could even do a complete chroot environment, with your path set the way you want, but it all comes down to the same thing. Have fun. That's not sarcastic, that's what this whole thing is supposed to be about, right? > > rone > -- > el mercado on the corner has grande bags of clues rilly cheapo. > - Patrick J. Finerty <pfinerty@nyx10.nyx.net> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-ports" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9906012354240.82061-100000>