aboutsummaryrefslogtreecommitdiff
path: root/winsup/doc
diff options
context:
space:
mode:
authorDavid Starks-Browning <starksb@ebi.ac.uk>2000-10-18 15:16:45 +0000
committerDavid Starks-Browning <starksb@ebi.ac.uk>2000-10-18 15:16:45 +0000
commitf1d9a0d4797253a323bc883d0146957977b31b97 (patch)
tree558b6cc0b7dc2b13d3937d9550db6c5536c2f6b6 /winsup/doc
parentb55af6accd54d389e595828a22aae34d2379865b (diff)
downloadnewlib-f1d9a0d4797253a323bc883d0146957977b31b97.zip
newlib-f1d9a0d4797253a323bc883d0146957977b31b97.tar.gz
newlib-f1d9a0d4797253a323bc883d0146957977b31b97.tar.bz2
Minor update to "How can I find out which dlls are needed by an executable?",
indicate that cygcheck works recursively.
Diffstat (limited to 'winsup/doc')
-rw-r--r--winsup/doc/how-programming.texinfo4
1 files changed, 2 insertions, 2 deletions
diff --git a/winsup/doc/how-programming.texinfo b/winsup/doc/how-programming.texinfo
index 8b2ecfe..e921054 100644
--- a/winsup/doc/how-programming.texinfo
+++ b/winsup/doc/how-programming.texinfo
@@ -243,8 +243,8 @@ gcc as:
@samp{objdump -p} provides this information, but is rather verbose.
-@samp{cygcheck} will do this much more concisely, provided the command
-is in your path.
+@samp{cygcheck} will do this much more concisely, and operates
+recursively, provided the command is in your path.
Note there is currently a bug in cygcheck in that it will not report
on a program in a Windows system dir (e.g., C:\Windows or C:\WINNT) even