Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 5 Nov 2003 12:40:09 +0100 From: "Gerrit P. Haase" Reply-To: "Gerrit P. Haase" Organization: Esse keine toten Tiere X-Priority: 3 (Normal) Message-ID: <5311426515.20031105124009@familiehaase.de> To: Milton Woods CC: cygwin@cygwin.com Subject: Re: Cygwin gcc-3.3.1 and pragma interface/implementation statements In-Reply-To: <3FA88BC9.8090902@adelaide.edu.au> References: <3FA88BC9.8090902@adelaide.edu.au> MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Hello Milton, Wednesday, November 5, 2003, 6:34:01 AM, you wrote: > Greetings, > When building LyX version 1.3.x from source on Cygwin, I had problems > during the final link stage where gcc-3.3.1 reported some undefined > symbols. All of the 'undefined' symbols were actually defined in the LyX > source code, and the compilation proceeded without errors on Linux. I > found that the compilation was also successful on Cygwin once the > #pragma interface/implementation statements were removed from the LyX > source code. The LyX developers had taken reasonable care to protect the > #pragma statements from incompatible compilers by using "#ifdef __GNUG__ > " wrappers, but that did not seem to be good enough. It is a known issue that #pragma interface/implementation doesn't work with Cygwin g++, no solution/fix is known yet. > Does this experience reflect a bug in the gcc toolchain? Or are the LyX > developers using #pragma statements incorrectly? No, it is ok with linux. -- Best regards, Gerrit -- 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/