This is the mail archive of the cygwin mailing list for the Cygwin 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: Redirecting stderr to stdout through pipe doesn't work the way it does in Linux


On 12/5/2018 5:25 PM, David Karr wrote:
On Wed, Dec 5, 2018 at 11:44 AM cyg Simple <cygsimple@gmail.com> wrote:

On 12/5/2018 1:33 PM, David Karr wrote:
On Wed, Dec 5, 2018 at 9:43 AM cyg Simple <cygsimple@gmail.com> wrote:


Your query got me interested in looking and I believe that winpty needs
to be at the front of all the commands so that it can communicate with
mintty properly.  To overcome the need to remember you could add an
alias to execute the command; `alias FOO="winpty FOO"'.


Sigh. What a mess. I can't get this to work.  It was easy enough when a
single script has to execute "kubectl", having "winpty" prefix that call,
but I'm trying to write a script that calls that other script, and even
in
a pipeline.

If I have "winpty" prefix the call to the script that calls "kubectl", it
says:

      winpty: error: cannot start '...': Not found in PATH

When I changed it so it references the absolute path, it then says "%1 is
not a valid Win32 application. (error 0xc1)".  So, this makes it clear
that
winpty can only directly execute Windows applications, which makes sense.

So how can I call a Windows application from more than just the top-level
script?


What does cygcheck say about your winpty?  You are using the Cygwin
compiled version, correct?


By "say", I assume you mean the output from running "cygcheck winpty"?
This is what I get:


Yes that is what I meant by my colloquial phrase.

     Found:
C:\Users\myuid\frameworks\winpty-0.4.3-cygwin-2.8.0-x64\bin\winpty.exe
     C:\Users\myuid\frameworks\winpty-0.4.3-cygwin-2.8.0-x64\bin\winpty.exe
       C:\cygwin64\bin\cygwin1.dll
         C:\Windows\system32\KERNEL32.dll
           C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
           C:\Windows\system32\ntdll.dll
           C:\Windows\system32\KERNELBASE.dll
           C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
           C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll
       C:\Users\myuid\frameworks\winpty-0.4.3-cygwin-2.8.0-x64\bin\winpty.dll
         C:\Windows\system32\ADVAPI32.dll
           C:\Windows\system32\msvcrt.dll
             C:\Windows\system32\API-MS-Win-Core-Console-L1-1-0.dll
             C:\Windows\system32\API-MS-Win-Core-DateTime-L1-1-0.dll
           C:\Windows\system32\API-MS-WIN-Service-Core-L1-1-0.dll
           C:\Windows\system32\API-MS-WIN-Service-winsvc-L1-1-0.dll
           C:\Windows\system32\API-MS-WIN-Service-Management-L1-1-0.dll
           C:\Windows\system32\API-MS-WIN-Service-Management-L2-1-0.dll
           C:\Windows\system32\API-MS-Win-Core-LocalRegistry-L1-1-0.dll
           C:\Windows\system32\RPCRT4.dll
             C:\Windows\system32\API-MS-Win-Core-Interlocked-L1-1-0.dll
             C:\Windows\system32\API-MS-Win-Core-DelayLoad-L1-1-0.dll
         C:\Windows\system32\USER32.dll
           C:\Windows\system32\GDI32.dll
             C:\Windows\system32\LPK.dll
               C:\Windows\system32\USP10.dll


I see nothing wrong here, time to ask winpty community what might be wrong.

--
cyg Simple

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


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