On Monday 22 March 2010 21:47:53 Chet Ramey wrote:
> The attached patch fixes it for me. Let me know.
that seems to work for me too, thanks
-mike
signature.asc
Description: This is a digitally signed message part.
On 3/22/10 6:21 PM, Mike Frysinger wrote:
> ok, the trouble is that we take the code, save it via `set`, and then restore
> it.
OK, that was the missing piece. Not really anything to do with the
redirection code per se.
> the assumption is that what bash outputs is equivalent to the original
>
ok, the trouble is that we take the code, save it via `set`, and then restore
it. the assumption is that what bash outputs is equivalent to the original
code. bash-4 though does not provide equivalent code.
so here is the reduced test case:
$ cat test.sh
foo() {
rm -f a b c
for
> > > when i strace bash, i see both files being opened, set to stdout, and
> > > then cat executed, but only in the first file (src/assembler.S) does
> > > there appear to be any data waiting for cat on stdin. the second file's
> > > cat reads stdin and gets back 0 bytes.
> > >
> > > trying to d
On Sunday 21 March 2010 21:21:36 Chet Ramey wrote:
> On 3/21/10 1:55 AM, Mike Frysinger wrote:
> > i have a small bit of code in a function:
> > foo() {
> >
> > local f
> > for f in src/assembler.S src/assembler_opt.S ; do
> >
> > cat <<-EOF >> ${f}
> > #ifdef
On 3/21/10 1:55 AM, Mike Frysinger wrote:
> i have a small bit of code in a function:
> foo() {
> local f
> for f in src/assembler.S src/assembler_opt.S ; do
> cat <<-EOF >> ${f}
> #ifdef __ELF__
> .section .note.GNU-stack,"",%progbits
>