On 4/15/2015 12:02 PM, Keith Christian wrote:
cygcheck attachment is too large according to sourceware.
What specific parts of cygcheck are needed to help troubleshoot this?
Keith
On Wed, Apr 15, 2015 at 12:55 PM, Keith Christian
<keith1christ...@gmail.com> wrote:
Both /usr/bin/dig and /bin/dig run the same program:
cksum /usr/bin/dig /bin/dig
680300229 2202141 /usr/bin/dig
680300229 2202141 /bin/dig
Attached cygcheck_s_r_v_kvc.txt.
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.
Good luck.
On Tue, Apr 14, 2015 at 3:53 PM, Mark Hansen<m...@winfirst.com> wrote:
Are you sure that you're getting the correct dig executable? Is it possible
that something else in
your path or alias list is getting hit? Perhaps you can try /usr/bin/dig
just to be sure?
--
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
