Cygwin gcc-3.3.1 and pragma interface/implementation statements

Cygwin gcc-3.3.1 and pragma interface/implementation statements

[Milton Woods]

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.

Does this experience reflect a bug in the gcc toolchain? Or are the LyX 
developers using #pragma statements incorrectly?

Milton Woods.



--
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/

Re: Cygwin gcc-3.3.1 and pragma interface/implementation statements

[Gerrit P. Haase]

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/