From owner-freebsd-questions Fri Jan 10 04:49:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA10067 for questions-outgoing; Fri, 10 Jan 1997 04:49:33 -0800 (PST) Received: from zxcv-pc.jumpnet.com (zxcv-pc.jumpnet.com [207.8.37.178]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA10062; Fri, 10 Jan 1997 04:49:30 -0800 (PST) Received: from zxcv-pc (localhost [127.0.0.1]) by zxcv-pc.jumpnet.com (8.7.5/8.7.3) with SMTP id GAA14264; Fri, 10 Jan 1997 06:49:02 -0600 (CST) Date: Fri, 10 Jan 1997 06:48:56 -0600 (CST) From: Curt Finch To: bugs@freebsd.org, questions@freebsd.org Subject: Re: python problems on freebsd (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk this occurs when installing and compiling python from ftp.python.org on freebsd2.1.5 (maybe fixed on latest?) _______________________________________________________________________ | Curt Finch Phoenix Net-Tek LLC 512-795-0709 | ----------------------------------------------------------------------- ---------- Forwarded message ---------- Date: Fri, 10 Jan 1997 15:37:40 +1100 From: Stephen Robert Norris To: Curt Finch Subject: Re: python problems on freebsd Newsgroups: comp.lang.python Curt Finch wrote: > > it's just the sed distributed w/ freebsd, i'm sure it's fine > i'll work on it and send out the real answer when i find it > > thanx for your input It isn't. Use GNU sed. I had exactly the same problem on a clients FreeBSD box, and using GNU sed fixed it completely. I wonder why FreeBSD has a broken sed? Stephen