From owner-freebsd-current Mon Aug 4 10:51:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA15532 for current-outgoing; Mon, 4 Aug 1997 10:51:18 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA15517 for ; Mon, 4 Aug 1997 10:51:01 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA04390; Mon, 4 Aug 1997 10:47:58 -0700 From: Terry Lambert Message-Id: <199708041747.KAA04390@phaeton.artisoft.com> Subject: Re: Make this a relese coordinator decision (was Re: ports-current/packages-current discontinued) To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 4 Aug 1997 10:47:57 -0700 (MST) Cc: andreas@klemm.gtn.com, dg@root.com, current@FreeBSD.ORG In-Reply-To: <20709.870682532@time.cdrom.com> from "Jordan K. Hubbard" at Aug 4, 97 01:15:32 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In -current? I forsee multiple architectures, each with their own > toolchain support (and this is going to be *fun* - NOT :-) and I see > the make system changing substantially to make it more self-contained. The toolchain stuff in GCC is broken. Sure, it hides everything under the huge, lumpy covers, but the bed you are expected to lie in looks like hell. The code generation needs to be decoupled at the quad level instead of where it is (bin*bletch*utils et. al.). I first complained about this in 1993, and submitted patches, which were rejected. Just like "brandelf" and "OLF". 8-(. Has anyone ever cross-compile for an NCR Tower XP on an NCR Tower 32? Now *THERE* was a reasonable cross-environment... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.