From owner-freebsd-ports Tue Feb 3 23:00:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29853 for freebsd-ports-outgoing; Tue, 3 Feb 1998 23:00:03 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: (from gnats@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29845; Tue, 3 Feb 1998 23:00:01 -0800 (PST) (envelope-from gnats) Date: Tue, 3 Feb 1998 23:00:01 -0800 (PST) Message-Id: <199802040700.XAA29845@hub.freebsd.org> To: freebsd-ports Cc: From: "Pedro F. Giffuni" Subject: Re: ports/5564: Update to the crosssco port Reply-To: "Pedro F. Giffuni" Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-ports" The following reply was made to PR ports/5564; it has been noted by GNATS. From: "Pedro F. Giffuni" To: freebsd-gnats-submit@freebsd.org, giffunip@asme.org Cc: Subject: Re: ports/5564: Update to the crosssco port Date: Wed, 04 Feb 1998 01:50:52 -0500 Using i386-coff limits the functionality of the port, but the update can't be built with i386-sco due to problems with our version of GNU as. The update is also required when we update the tools for an ELF environment. I suggest the new port (now in incoming) is committed after 2.2.6-R is out: It will build with both versions of the bintools, but lacks some of the support of the older version. When 3.0-R is out an even newer update can be done.