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: dig utility in bind-utils-9.9.7-1 returns no output

Greetings, Keith Christian!

>>> I'm sorry - I could be completely off-base here. What I meant was can you
>>> try running
>>> '/usr/bin/dig' (providing the full path to the application) rather than by
>>> just running 'dig'
>>> just in case there is some other 'dig' on your path (or shell aliases) which
>>> might be running
>>> rather than the actual /usr/bin/dig command.
>>> In previous messages, your examples were running 'dig' (without the full
>>> path) so it wasn't
>>> clear which dig you were actually getting.

>> Thanks Mark, but I tried both of those early in my attempts without
>> success.  Good suggestion, though.

> I updated Cygwin this morning, and now: "dig works!  I have no idea why!"

> "cksum /usr/bin/dig /bin/dig" reports the same checksums as before,
> and "cygcheck dig" produces the same output as before.

> Baffling.

I've seen similar effect, when Cygwin was going through implementation of some
specific POSIX calls, and export tables were bouncing around libs in the
But your claim that you've had Cygwin updated led the discussion sideways.
My bet was you've had Cygwin1.dll locked when updating and the update wasn't
completely successful.

> Thanks to all of you for the suggestions.

No problem.
However, please don't top-post in future.

With best regards,
Andrey Repin
Saturday, April 18, 2015 01:55:23

Sorry for my terrible english...

Problem reports:
Unsubscribe info:

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