From owner-freebsd-current Fri Mar 13 21:08:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11599 for freebsd-current-outgoing; Fri, 13 Mar 1998 21:08:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11594 for ; Fri, 13 Mar 1998 21:08:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id VAA03336; Fri, 13 Mar 1998 21:05:36 -0800 (PST) Message-Id: <199803140505.VAA03336@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: John Birrell cc: current@FreeBSD.ORG Subject: Re: binutils bloat In-reply-to: Your message of "Sat, 14 Mar 1998 16:04:35 +1100." <199803140504.QAA16504@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Mar 1998 21:05:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Erk. That's kinda ugly; this isn't something that could be trivially > > automated I suppose. > > It was born ugly (GPL). Automated? I'm not sure. Somewhere you have > to store the config and it's not just a matter of running `configure' ... or more to the point the configuration isn't a uniform item; it varies with target. So unless you have a list of known targets on hand, you can't do it "automatically". IMHO that's a pretty strong selection criteria for what to include from binutils; if there's a canned gas config for a target, then the files that target requires should be included. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message