From owner-freebsd-current Tue Sep 3 20: 8:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAD8E37B406 for ; Tue, 3 Sep 2002 20:08:11 -0700 (PDT) Received: from mail.speakeasy.net (mail16.speakeasy.net [216.254.0.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6C4943E3B for ; Tue, 3 Sep 2002 20:08:09 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 5830 invoked from network); 4 Sep 2002 03:08:39 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail16.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 4 Sep 2002 03:08:39 -0000 Received: from laptop.baldwin.cx (laptop.baldwin.cx [192.168.0.4]) by server.baldwin.cx (8.12.5/8.12.5) with ESMTP id g84388Bv006158; Tue, 3 Sep 2002 23:08:08 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200209032347.TAA25289@warspite.cnchost.com> Date: Tue, 03 Sep 2002 23:08:08 -0400 (EDT) From: John Baldwin To: Bakul Shah Subject: Re: aout support broken in gcc3 Cc: current@FreeBSD.ORG, Julian Elischer , Juli Mallett , Richard Tobin , Maxim Sobolev Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 03-Sep-2002 Bakul Shah wrote: >> > > Where exactly does GCC fit into the mix, making this impossible? >> > >> > They compile Lisp (etc) to a C file, which they compile (with gcc) to >> ^^^ >> actually with as(1), because gcc is only generates assembler file, >> which is then translated into the object file by assembler (as). >> Assembler by itself is part of binutils, not a compiler suite. > > I suspect Richard Tobin was using the generally accepted > meaning for a "compiler" as one that translates a source > program into object code (machine language). In any case, it > is cc1 that generates an assembly file. gcc is just a driver > program that calls various subprograms. > > Richard's main point with which I totally agree is that > please do not take away the ability to generate and grok > a.out files *if at all possible*. A number of Lisp systems > as well as Scheme one use ld -A & friends to do what he > described. In general, please do not break backward > compatibility. > > > Seems to me that most of the FreeBSD developers are not heavy > 3rd part software users. Consequently they (the developers) > do not realize that even when sources are available it is not > always easy to update them to support changes that break old > code -- due to lack of time or money or inability or > inexperience to change the 3rd party software or whatever. > When sources are not available, you are up the proverbial > creek. > > You may say just continue running old freeBSD kernels but the > constant stream of security fixes makes hard to justify doing > that. You are blowing this out of proportion and not actually reading what people are proposing. So far, the comments are about removing a.out support from the base compiler and offering a.out binutils and gcc _as ports_. Thus, people who needed to work with a.out can still install a toolchain to work with, they just wouldn't use the toolchain in the base system. The toolchain in the base system would then be easier to maintain resulting in it being more up-to-date and it would also be a bit faster. > Unfortunately there is no such direct back-pressure in the > open source community and developers usually don't have a > long term view. Thank you for insulting our intelligence. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message