From owner-freebsd-arch Wed Oct 24 19:22: 6 2001 Delivered-To: freebsd-arch@freebsd.org Received: from atg.aciworldwide.com (h139-142-180-4.gtcust.grouptelecom.net [139.142.180.4]) by hub.freebsd.org (Postfix) with ESMTP id 1A78837B403 for ; Wed, 24 Oct 2001 19:22:04 -0700 (PDT) Received: from atg.aciworldwide.com (atg.aciworldwide.com [139.142.180.33]) by atg.aciworldwide.com (8.12.0/8.12.0) with ESMTP id f9P2M30H071765 for ; Wed, 24 Oct 2001 20:22:03 -0600 (MDT) Message-Id: <200110250222.f9P2M30H071765@atg.aciworldwide.com> To: arch@freebsd.org Subject: X-URL: http://www.aciworldwide.com/ X-Notes-Item: Just say NO to Notes! Organization: ACI Worldwide - Advanced Technology Group Date: Wed, 24 Oct 2001 20:22:03 -0600 From: Lyndon Nerenberg Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alfred Perlstein mentioned that these messages might be more appropriate for arch. (I wasn't sure ...) ------- Forwarded Message To: hackers@freebsd.org Subject: GCC/G++ links Date: Wed, 24 Oct 2001 20:17:07 -0600 From: Lyndon Nerenberg [ On a related somewhat anti-GNU thread ... ] 18 months ago we had a conversation on the mailing list about g77 vs. f77 as the canonical command name for the FORTRAN compiler. The crux of the argument was that f77 was the canonical BSD name for the command, and that's what it has been since. There was a related argument as to whether gcc (as a name) should die as well, but the argument was made that too many third party packages would break as a result. For the last year I've been running my systems with the gcc and g++ links to the respective binaries removed, and I haven't seen much break as a result, other than a (very) few ports which were fixed with a quick edit of their Makefile. Meanwhile, it has been useful to install different versions of the GNU C compiler, and in those cases it has also been useful to call them by their real names: gcc and g++. Practical experience shows that cc and gcc can live side-by-side. And also shows that the base OS environment lives well without the GNU naming conventions. 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.) - --lyndon ------- End of Forwarded Message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message