From owner-freebsd-current@FreeBSD.ORG Fri Jun 13 12:56:53 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB89837B401 for ; Fri, 13 Jun 2003 12:56:53 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B3A743F85 for ; Fri, 13 Jun 2003 12:56:52 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from athlon.pn.xcllnt.net (athlon.pn.xcllnt.net [192.168.4.3]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h5DJuohS035019; Fri, 13 Jun 2003 12:56:50 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from athlon.pn.xcllnt.net (localhost [127.0.0.1]) by athlon.pn.xcllnt.net (8.12.9/8.12.9) with ESMTP id h5DJuoLg000721; Fri, 13 Jun 2003 12:56:50 -0700 (PDT) (envelope-from marcel@athlon.pn.xcllnt.net) Received: (from marcel@localhost) by athlon.pn.xcllnt.net (8.12.9/8.12.9/Submit) id h5DJuoRm000720; Fri, 13 Jun 2003 12:56:50 -0700 (PDT) Date: Fri, 13 Jun 2003 12:56:50 -0700 From: Marcel Moolenaar To: Fish Message-ID: <20030613195650.GA650@athlon.pn.xcllnt.net> References: <1055533340.57537.16.camel@current> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1055533340.57537.16.camel@current> User-Agent: Mutt/1.5.4i cc: freebsd-current@freebsd.org Subject: Re: Buildworld failing in /usr/src/gnu/usr.bin/binutils/libbfd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jun 2003 19:56:54 -0000 On Fri, Jun 13, 2003 at 03:42:20PM -0400, Fish wrote: > Hello list, > > I'm sure I've done something naughty as I've been seeing errors for a > few days, but I've done some troubleshooting and I can't seem to find > the place I shot myself in the foot. This is getting a FAQ; I'll add an entry to UPDATING. There was a small window in which sed(1) was broken. If you happen to have installed sed(1) during that window, which you apparently have, you need to manually build and install sed(1) (and only sed(1))\ before doing anything else. > Would someone please tell me exactly what stupid thing I'm doing today? You forgot to search the mailing list :-) -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net