From: "Paul Derbyshire" <derbyshire@globalserve.net>
To: cygwin@cygwin.com
Subject: Missing libc documentation
Date: Fri, 26 Jul 2002 02:14:00 -0000 [thread overview]
Message-ID: <3D408184.12752.478AF1AB@localhost> (raw)
I'm not sure how, but the libc documentation in my system is missing.
It was there this morning, and the only thing I've done since then
that might affect documentation was to use cygwin setup, but I used
it to upgrade some packages and install new documentation, not
uninstall anything, so nothing should have *dis*appeared. Also,
nobody else has had physical access to the box all day. So, can
anyone explain how this could have happened?
It gets worse. Reinstalling the "texinfo" package, all 600K of it,
did not bring back my "info libc". I suppose I have to reinstall some
other package to restore the libc documentation. Could someone please
tell me which one? And please let it not be the multi-megabyte gcc
package. Please.
Finally, if anyone has any idea how the documentation got destroyed,
I'd appreciate any information you can give about how to prevent this
from happening again. (Especially if it does mean reinstalling the
mutli-megabyte gcc package.) Is it typical for cygwin to go eating
files at random? Should I be backing up my home directory outside of
the cygwin directory? (If it decides to disappear, weeks of work will
be lost.)
It's particularly strange that this would happen to a system that's
completely up to date -- a serious bug that causes files to vanish
and/or messes up documentation browsing is the sort I'd expect to
occur only with outdated buggy old stuff sitting around.
In the meantime I suppose I can use DJGPP's libc documentation and
hope the stdio functions are basically the same. (Should be; they are
a standardized part of ANSI C.)
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2002-07-26 2:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 2:14 Paul Derbyshire [this message]
2002-07-26 4:44 Demmer, Thomas
2002-07-26 6:52 Demmer, Thomas
2002-07-26 8:21 ` Robert Collins
2002-07-26 7:58 Demmer, Thomas
2002-07-26 14:31 ` Paul Derbyshire
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D408184.12752.478AF1AB@localhost \
--to=derbyshire@globalserve.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).