X-Spam-Check-By: sourceware.org Message-ID: <442A8E16.1060500@byu.net> Date: Wed, 29 Mar 2006 06:39:34 -0700 From: Eric Blake User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Please help on cscope15.5 compiling errors References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Hong Sun on 3/28/2006 10:24 PM: > Hi, > > I was not able to attach the cyhcheck.out file as it was bounced back as > spam. I'm not sure it was the cygcheck.out that triggered the filter, especially since most people have no problems in attaching a file named just that; it could have been your choice of subject line, the use of HTML, or some other problem. However, you could try renaming the attachment cygcheck.txt and see if that helps. > Anyway, I got errors when compling cscope15.5 on cygwin 15.1.9-4 > downloaded on March 27,2006. The error compains that function getline() > was re-declared in cscope package's global.h, which was delcared in > cygwin's /usr/include/sys/stdio.h at line 31. This has been discussed previously on the list, in January and February. One option is for you to "#define readline rpl_readline" immediately after including stdio.h, but before any use of readline in your package, so that the two definitions don't conflict. The other option is to upgrade to a snapshot, including updated headers, where the cygwin getline is properly guarded behind the _GNU_SOURCE feature test. > > I commented out line 31 in stdio but still got other errors. Since I > complied and installed cscope15.5 on previous cygwin release in 2003, it > might be a bug in cygwin 1.5.19-4. Changing system headers that don't belong to your package, in order to get your package to compile, is usually a very risky effort that should not normally be attempted. - -- Life is short - so eat dessert first! Eric Blake ebb9 AT byu DOT net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEKo4W84KuGfSFAYARAl/xAJ9D851eXk3wOu+wygzAnNgOO4prAACfeeot Giji3v2Oiz5xjA0wD2zl/ak= =83I5 -----END PGP SIGNATURE----- -- 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/