Date: Fri, 26 Oct 2001 19:29:34 +0300 From: Giorgos Keramidas <charon@labs.gr> To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> Cc: Lyndon Nerenberg <lyndon@atg.aciworldwide.com>, arch@FreeBSD.org Subject: Re: your mail Message-ID: <20011026192933.B16134@hades.hell.gr> In-Reply-To: <20011026153313.C96876@daemon.ninth-circle.org> References: <200110250222.f9P2M30H071765@atg.aciworldwide.com> <20011026153313.C96876@daemon.ninth-circle.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 26, 2001 at 03:33:13PM +0200, Jeroen Ruigrok/Asmodai wrote: > >Based on this, what do you think about adding a NO_GNU_COMPLER_CMD_LINKS > >macro to make.conf? If set, if would prevent the linking of cc -> > >gcc and c++ -> g++, freeing up /usr/local/bin/g* for the site to > >decide? (And I'm not tied to that horribly long macro name, either.) > > I would sooner prefer the other way around. Have gcc and g++ and have a > knob to not create the gcc -> cc symlink. :) No please. I don't mind having both cc and gcc on my disks, but `cc' is the name of the system compiler. Since our system compiler is gcc, I'd expect both links to exist. Having a compiled named gcc is a GNU'ism that has stuck with us now, but having a compiler called cc is something that is part of what I've learned to call Unix. -giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011026192933.B16134>