From owner-freebsd-current Thu Dec 9 2:57:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 6651D15315 for ; Thu, 9 Dec 1999 02:57:33 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id LAA25818 for current@FreeBSD.org; Thu, 9 Dec 1999 11:35:59 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Thu, 09 Dec 1999 11:35:54 +0100 From: Marcel Moolenaar Message-ID: <384F860A.499A29EA@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <19991209163452O.shigeru@iij.ad.jp>, <199912090800.RAA01655@tomoyo.snipe.rim.or.jp> Subject: Re: why 'The legacy aout build' was removed from current ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Motoyuki Konno wrote: > I also wonder why a.out support was removed from -current. a.out support has not been removed. We just don't do any legacy a.out building. > I think we don't need "a.out world" any more, but a.out support > (a.out lib/shared lib, etc.) is still needed. For this, the proper compat distribution should/can be installed. > Some commercial > programs such as Netscape are in a.out only, so we still have to > make a.out binaries. No, we only have to *run* them. This we do. If Netscape were to compile on -current, they would have an ELF version... > Please see Netscape plugin port (ports/www/flashplugin) to find > out why we still have to need a.out support. The port has nothing to do with building a legacy a.out world and consequently works fine (yes, I tested it :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message