[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: patch

From: Donald Sharp
Subject: Re: patch
Date: Fri, 3 Nov 2000 16:22:54 -0500
User-agent: Mutt/1.2.4i

On Fri, Nov 03, 2000 at 04:13:43PM -0500, Larry Jones wrote:
> Donald Sharp writes:
> > 
> > An actual problem with sed( /usr/ucb/sed ) in backuprecover-22.  
> What version of CVS are you using?  As far as I can see,

I'm using 1.11:
donsharp-u5:114> cvs status src/
File:         Status: Locally Modified

   Working revision:    1.621
   Repository revision: 1.621   /home2/cvsroot/ccvs/src/,v
   Sticky Tag:          cvs1-11 (revision: 1.621)
   Sticky Date:         (none)
   Sticky Options:      (none)

Here is the errors spat out:

sed: Unrecognized command: file1
sed: Extra text at end of command: dir/file2
sed: Extra text at end of command: dir/file2 
sed: Unrecognized command: file1
FAIL: backuprecover-22
make[1]: *** [check] Error 1
make[1]: Leaving directory `/users/sharpd/distrib/ccvs/src`
make: *** [check] Error 2

This problem goes away when I used the gnu version of sed.

I still have the cvs-sanity test directory around, would you like
to see any particular data in there?

> backuprecover-22 doesn't use sed.  And it looks to me like even sed from
> 7th Edition Unix (which is usually held up as the standard for
> portability) could handle everything from
> > I guess my biggest complaint is that is completely dependent
> > on your path, and that I don't see a real good way of getting around
> > this problem....
> That's not a problem, it's a feature!  (And the way you get around it is

or something ;)

> by changing the path; if not for you, at least for

> -Larry Jones
> I just can't identify with that kind of work ethic. -- Calvin

reply via email to

[Prev in Thread] Current Thread [Next in Thread]