Re: dig and host not returning output in bind-utils-9.10.2-1

2015-06-19 Thread Keith Christian
On Fri, Jun 19, 2015 at 3:36 PM, Yaakov Selkowitz wrote: > On Fri, 2015-06-19 at 14:24 -0600, Keith Christian wrote: >> Updated to bind-utils-9.10.2-1 and neither dig nor host returns >> output. There is a pause of about 0.7 seconds while dig runs. >> >> Strace shows quite a bit of dig activity b

Re: dig and host not returning output in bind-utils-9.10.2-1

2015-06-19 Thread Yaakov Selkowitz
On Fri, 2015-06-19 at 14:24 -0600, Keith Christian wrote: > Updated to bind-utils-9.10.2-1 and neither dig nor host returns > output. There is a pause of about 0.7 seconds while dig runs. > > Strace shows quite a bit of dig activity but nothing returned. > > Anyone else having this issue? WFM.

Re: perl 5.14 perl5/5.14/i686-cygwin-threads-64int/auto/IO/IO.dll missing or broken

2015-06-19 Thread Marco Atzeri
On 6/19/2015 11:05 PM, Daniel wrote: Marco Atzeri wrote: On 6/19/2015 7:34 AM, Daniel wrote: William J. Schilp, PhD wrote: please use cygcheck /usr/lib/perl5/5.14/i686-cygwin-threads-64int/auto/IO/IO.dll It will tell you what other dll's is missing I included the cygcheck output. The

Re: perl 5.14 perl5/5.14/i686-cygwin-threads-64int/auto/IO/IO.dll missing or broken

2015-06-19 Thread Daniel
Marco Atzeri wrote: On 6/19/2015 7:34 AM, Daniel wrote: William J. Schilp, PhD wrote: I have the same problem (I'm on 32bit). The IO module is broken: $ ldd /usr/lib/perl5/5.14/i686-cygwin-threads-64int/auto/IO/IO.dll ntdll.dll => /cygdrive/c/WINDOWS/system32/ntdll.dll (0x7c90)

dig and host not returning output in bind-utils-9.10.2-1

2015-06-19 Thread Keith Christian
Tried to continue the previous thread but large attachments destroyed the thread. Updated to bind-utils-9.10.2-1 and neither dig nor host returns output. There is a pause of about 0.7 seconds while dig runs. Strace shows quite a bit of dig activity but nothing returned. Anyone else having this

Re: perl 5.14 perl5/5.14/i686-cygwin-threads-64int/auto/IO/IO.dll missing or broken

2015-06-19 Thread Marco Atzeri
On 6/19/2015 7:34 AM, Daniel wrote: William J. Schilp, PhD wrote: I have the same problem (I'm on 32bit). The IO module is broken: $ ldd /usr/lib/perl5/5.14/i686-cygwin-threads-64int/auto/IO/IO.dll ntdll.dll => /cygdrive/c/WINDOWS/system32/ntdll.dll (0x7c90) kernel32.dll =>

Re: Arguments parsing in cygwin executables

2015-06-19 Thread Andrey Repin
Greetings, Corinna Vinschen! >> > BTW, in CYGWIN=glob mode, curly braces are handled wrongly >> > (c:\cygwin\echo.exe {aa} should return {aa}, not aa; because no , or >> > .. inside {}). >> >> I don't think so. GLOB_BRACE globbing is meant to do brance globbing >> just as csh does. This doesn't

Re: Arguments parsing in cygwin executables

2015-06-19 Thread Corinna Vinschen
On Jun 19 10:44, Corinna Vinschen wrote: > Hi Sasha, > > On Jun 17 20:56, Sasha Unknown wrote: > > Hello. > > > > ==Preamble== > > Some time ago I noticed that cygwin executables (e.g. bash, tar, echo > > & so on) handle specially *, {} and some other symbols in > > command-line, even when being

Re: Arguments parsing in cygwin executables

2015-06-19 Thread Corinna Vinschen
Hi Sasha, On Jun 17 20:56, Sasha Unknown wrote: > Hello. > > ==Preamble== > Some time ago I noticed that cygwin executables (e.g. bash, tar, echo > & so on) handle specially *, {} and some other symbols in > command-line, even when being invoked not from shell (e.g. > programmatic invocation or c