Alastair McKinstry writes ("Re: 'tty' output on kFreeBSD, etc. within sbuild"):
> On 06/01/2014 12:39, Ian Jackson wrote:
> > But perhaps more information would enable us to give better advice.
>
> Thanks, I've been able to adapt the build scripts so it
On 06/01/2014 12:39, Ian Jackson wrote:
> Alastair McKinstry writes ("'tty' output on kFreeBSD, etc. within sbuild"):
>> Can anyone answer the following question which is puzzling me;
>> I have a piece of csh code which gets called during the build of a pack
Alastair McKinstry writes ("'tty' output on kFreeBSD, etc. within sbuild"):
> Can anyone answer the following question which is puzzling me;
> I have a piece of csh code which gets called during the build of a package
> i'm maintaining. it does the following:
>
On Fri, Jan 03, 2014 at 07:12:51PM +, Roger Leigh wrote:
> You aren't guaranteed to have a controlling terminal, particularly when
> run via buildd. So while stdin/out/err are all connected and
> functional, they are either null (stdin) or pipes (out/err). If you
> need to output anything, th
On Fri, Jan 03, 2014 at 06:51:08PM +, Alastair McKinstry wrote:
> Can anyone answer the following question which is puzzling me;
> I have a piece of csh code which gets called during the build of a package
> i'm maintaining. it does the following:
>
> echo "useful information" > /dev/tty
>
>
Hi,
Can anyone answer the following question which is puzzling me;
I have a piece of csh code which gets called during the build of a package
i'm maintaining. it does the following:
echo "useful information" > /dev/tty
within the script. (stdout, stderr being redirected, I think).
This fails on
6 matches
Mail list logo
