Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: Date: Sun, 23 Jan 2005 22:03:06 -0800 From: Joshua Daniel Franklin Reply-To: Joshua Daniel Franklin To: Steve Munson , cygwin AT cygwin DOT com Subject: Re: 1.5.12-1: documentation bug in lib[cm].texinfo In-Reply-To: <12663890.1106396311862.JavaMail.root@wamui06.slb.atl.earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <12663890 DOT 1106396311862 DOT JavaMail DOT root AT wamui06 DOT slb DOT atl DOT earthlink DOT net> X-IsSubscribed: yes On Sat, 22 Jan 2005 07:18:31 -0500 (GMT-05:00), Steve Munson wrote: > From the info dir file in /usr/share/info, you can't get to the info > files for libc or libm, because their entries are wrong. The file > cygwin-1.5.12-1/newlib/libc/libc.texinfo in the source distribution > for cygwin-1.5.12-1 contains the following lines near the top of the > file: > > START-INFO-DIR-ENTRY > * libc:: The ANSI C library. > END-INFO-DIR-ENTRY > > This incorrectly instructs info to look for a node named "libc", > which doesn't exist. The correct entry would be: > > * libc: (libc). The ANSI C library. > > This tells info to look for the *file* libc.info. There is a similar > problem in cygwin-1.5.12-1/newlib/libm/libm.texinfo: > > START-INFO-DIR-ENTRY > * libm:: An ANSI-C conforming mathematical library. > END-INFO-DIR-ENTRY > > This entry, of course, should read: > > * libm: (libm). An ANSI-C conforming mathematical library. > Thanks Steve. Problem 1 is that these files come from newlib. Problem 2 is that they're in both cygwin and cygwin-doc. When did they get back into the "cygwin" package? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/