From owner-freebsd-ports Wed Aug 9 13: 4:16 2000 Delivered-To: freebsd-ports@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id 6E87A37B5DD; Wed, 9 Aug 2000 13:04:11 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-238.ix.netcom.com [209.109.235.238]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id QAA23691; Wed, 9 Aug 2000 16:04:07 -0400 (EDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id NAA17660; Wed, 9 Aug 2000 13:04:05 -0700 (PDT) To: John Baldwin Cc: Ade Lovett , ports@FreeBSD.ORG Subject: Re: Diking out ports a.out support References: <200008091930.MAA11858@pike.osd.bsdi.com> From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 09 Aug 2000 13:04:04 -0700 In-Reply-To: John Baldwin's message of "Wed, 9 Aug 2000 12:30:24 -0700 (PDT)" Message-ID: Lines: 16 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: John Baldwin * Granted, this requires you to populate /usr/lib/aout, but that is not * overly difficult. I have heard of people who use 4.0 aout only systems * in embedded work for some odd reason or another. I can see why checking to * insure that ports work as both aout and ELF binaries are painful. However, * ripping out all aout support seems drastic. I don't think that matters much. Most of the so-called "a.out support" in the ports system is for compiling an a.out/ELF binary on an ELF/a.out system, or for installing an a.out/ELF package on an ELF/a.out system. The latter will not happen for embedded people and they are capable of setting their CC etc. properly to handle the former. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message