From owner-freebsd-alpha Thu Apr 15 11:38:30 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 3CF8B14BD5 for ; Thu, 15 Apr 1999 11:38:22 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id OAA18946; Thu, 15 Apr 1999 14:35:35 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA97973; Thu, 15 Apr 1999 14:35:33 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 15 Apr 1999 14:35:32 -0400 (EDT) To: mjacob@feral.com Cc: Mike Smith , alpha@FreeBSD.ORG Subject: Re: egcs ready for alpha? In-Reply-To: References: <199904151804.LAA03139@dingo.cdrom.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14102.12407.996679.381089@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > It was more a question of can I now give up the gcc2.7.2.1 compiler and > expect to keep being able to work on the Fibre Channel driver (a daily > ritual). The only problem I've seen that could be a show-stopper for you is the fact that /sbin/dump produces corrupt dumps when built with egcs. You might want to keep a dump binary laying around. I'm not working on this (my plate it far too full right now) and I'd very much appreciate it if somebody could look into it.. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message