This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Don't pass shell loops' stdin to programs run on glibc's host

From: Roland McGrath <roland at hack dot frob dot com>
To: "Joseph S. Myers" <joseph at codesourcery dot com>
Cc: <libc-alpha at sourceware dot org>
Date: Mon, 22 Oct 2012 09:45:07 -0700 (PDT)
Subject: Re: Don't pass shell loops' stdin to programs run on glibc's host
References: <Pine.LNX.4.64.1210200012540.11460@digraph.polyomino.org.uk><20121020204428.982192C084@topped-with-meat.com><Pine.LNX.4.64.1210212239170.1291@digraph.polyomino.org.uk>

> where within the loop the shell's input is redirected - and the "read" 
> command, but not the test programs, should see that redirection.  Putting 
> "< /dev/null" at the top of the script, or in the makefiles, won't help 
> here.

I see.  That makes sense.

Follow-Ups:
- Re: Don't pass shell loops' stdin to programs run on glibc's host
  - From: Joseph S. Myers

References:
- Don't pass shell loops' stdin to programs run on glibc's host
  - From: Joseph S. Myers
- Re: Don't pass shell loops' stdin to programs run on glibc's host
  - From: Roland McGrath
- Re: Don't pass shell loops' stdin to programs run on glibc's host
  - From: Joseph S. Myers

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]