Date: Thu, 10 Oct 2002 15:26:28 -0400 From: "Eric L. Howard" <elh@outreachnetworks.com> To: freebsd-stable@FreeBSD.ORG Subject: Re: New sed breaks ports Message-ID: <20021010152628.A18833@outreachnetworks.com> In-Reply-To: <3DA5C638.10605@potentialtech.com>; from wmoran@potentialtech.com on Thu, Oct 10, 2002 at 02:26:00PM -0400 References: <FE045D4D9F7AED4CBFF1B3B813C8533701022C2D@mail.sandvine.com> <3DA5C638.10605@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At a certain time, now past, Bill Moran spake thusly:
> Don Bowman wrote:
> > try
> >
> > make REINPLACE_CMD="sed -i"
> > or
> > make REINPLACE_CMD="/usr/local/bin/sed_inplace"
> >
> > when you do the make for the port.
> >
> > I don't know why this is a problem, I've run into it
> > myself (on other ports).
>
> Thanks for the suggestion, but I continue to
> get the exact same error.
>
> On a related note, what is the shell magic to redirect
> both stdout and stderr to a file, I though it was:
>
> make REINPLACE_CMD="sed -i" 2>&1 > /dir/file.txt
You didn't say what shell your're using:
Bash and bourne - command > file 2>&1
> but apparently I've been in mousy/clicky land too
> long to remember my shell syntax. I want to capture
> the exact errors and formulate a better post, as I'm
> getting a lot of the same suggestions over and over.
Check out script(1).
$ script /var/tmp/script.output
$ command
.....
....
$ exit
$ less /var/tmp/script.output
~elh
--
Eric L. Howard e l h @ o u t r e a c h n e t w o r k s . c o m
------------------------------------------------------------------------
www.OutreachNetworks.com 313.297.9900
------------------------------------------------------------------------
Advocate of the Theocratic Rule
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021010152628.A18833>