From owner-freebsd-current Wed Dec 30 21:11:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20489 for freebsd-current-outgoing; Wed, 30 Dec 1998 21:11:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20484 for ; Wed, 30 Dec 1998 21:11:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id VAA14247; Wed, 30 Dec 1998 21:11:23 -0800 (PST) To: "Brian Haskin" cc: current@FreeBSD.ORG Subject: Re: New aout-to-elf build failures. In-reply-to: Your message of "Wed, 30 Dec 1998 22:32:32 EST." <000001be346e$3365a960$0b00000a@brianjr.haskin.org> Date: Wed, 30 Dec 1998 21:11:22 -0800 Message-ID: <14243.915081082@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok, as I'm not and haven't done any of the work I certainly don't have any > say, but just to add something that you might want to consider. I've been > thinking that it would be nice if the aout to elf build would be supported > till a little after the branch split. This would allow people following > stable the option of source upgrades the whole way through. But maybe this > adds to much "cruft" to the start of the new stable branch? I don't mind them following -current up to and after the branch, but they need to go ELF before that. It's just getting too difficult to support both worlds and I no longer even have a 3.0/a.out box handy here for testing such an environment. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message