From owner-freebsd-questions@FreeBSD.ORG Sat Sep 3 10:14:27 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A5DB16A41F for ; Sat, 3 Sep 2005 10:14:27 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out6.blueyonder.co.uk (smtp-out6.blueyonder.co.uk [195.188.213.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18F5343D45 for ; Sat, 3 Sep 2005 10:14:26 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [82.41.229.102] ([82.41.229.102]) by smtp-out6.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Sat, 3 Sep 2005 11:15:14 +0100 Message-ID: <43197781.1080204@dial.pipex.com> Date: Sat, 03 Sep 2005 11:14:25 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.8) Gecko/20050530 X-Accept-Language: en, en-us, pl MIME-Version: 1.0 To: Rein Kadastik References: <4318B54B.6080001@uninet.ee> <4318B66E.3010603@uninet.ee> <4318D90B.5030807@dial.pipex.com> <431954E6.1060802@uninet.ee> In-Reply-To: <431954E6.1060802@uninet.ee> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 03 Sep 2005 10:15:14.0397 (UTC) FILETIME=[600938D0:01C5B070] Cc: freebsd-questions@freebsd.org Subject: Re: sed not working X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2005 10:14:27 -0000 Rein Kadastik wrote: > Alex Zbyslaw wrote: > >> Rein Kadastik wrote: >> >>> >>> Rein Kadastik wrote: >>> >>>> Hi >>>> >>>> I have a problem with sed on one of my systems. >>> >>> >> You've probably tried this, but what does "which sed" show on the >> broken system? It should show /usr/bin/sed and if it doesn't, >> there's your problem :-) > > > It shows /usr/bin/sed > [...] > > The ident output is identical on the working system. I guess, that it > is some sort of a regex library issue, as sed itself does not contain > regex engine. Well, that was going to be my second guess :-) Do you have any extra compile options in /etc/make.conf which might be making something go wrong? Extra optimisations etc. --Alex