Re: FYI: Compiling lyx-1.04 with gcc-2.95.1 and X11R6.3
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | Lars Yes, I've heard about this problem... I do not know what a good Lars | solution would be in this case. A special case for gcc 2.95? I Lars am sure | other software projects have this problem too. It Lars would be interesting | to know how it has been fixed. Lars Note that this will also be a problem when the new C standard is Lars out, since it like C++ does not allow implicit return types on Lars functions. Lars The correct solution is for the X(Free) team to correct their Lars header files. Sure, but since it will not happen magically overnight, we have to find a workaround. JMarc
Re: FYI: Compiling lyx-1.04 with gcc-2.95.1 and X11R6.3
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | Sure, but since it will not happen magically overnight, we have to | find a workaround. The workaround is to run the compiler in a non-strict mode. I have seen that some compilers have -fpermissive. Lgb
Re: FYI: Compiling lyx-1.04 with gcc-2.95.1 and X11R6.3
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | Lars Yes, I've heard about this problem... I do not know what a good Lars | solution would be in this case. A special case for gcc 2.95? I Lars am sure | other software projects have this problem too. It Lars would be interesting | to know how it has been fixed. Lars Note that this will also be a problem when the new C standard is Lars out, since it like C++ does not allow implicit return types on Lars functions. Lars The correct solution is for the X(Free) team to correct their Lars header files. Sure, but since it will not happen magically overnight, we have to find a workaround. JMarc
Re: FYI: Compiling lyx-1.04 with gcc-2.95.1 and X11R6.3
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | Sure, but since it will not happen magically overnight, we have to | find a workaround. The workaround is to run the compiler in a non-strict mode. I have seen that some compilers have -fpermissive. Lgb
Re: FYI: Compiling lyx-1.04 with gcc-2.95.1 and X11R6.3
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | Lars> Yes, I've heard about this problem... I do not know what a good Lars> | solution would be in this case. A special case for gcc 2.95? I Lars> am sure | other software projects have this problem too. It Lars> would be interesting | to know how it has been fixed. Lars> Note that this will also be a problem when the new C standard is Lars> out, since it like C++ does not allow implicit return types on Lars> functions. Lars> The correct solution is for the X(Free) team to correct their Lars> header files. Sure, but since it will not happen magically overnight, we have to find a workaround. JMarc
Re: FYI: Compiling lyx-1.04 with gcc-2.95.1 and X11R6.3
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | Sure, but since it will not happen magically overnight, we have to | find a workaround. The workaround is to run the compiler in a non-strict mode. I have seen that some compilers have -fpermissive. Lgb
Re: FYI: Compiling lyx-1.04 with gcc-2.95.1 and X11R6.3
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | Yes, I've heard about this problem... I do not know what a good | solution would be in this case. A special case for gcc 2.95? I am sure | other software projects have this problem too. It would be interesting | to know how it has been fixed. Note that this will also be a problem when the new C standard is out, since it like C++ does not allow implicit return types on functions. The correct solution is for the X(Free) team to correct their header files. Lgb
Re: FYI: Compiling lyx-1.04 with gcc-2.95.1 and X11R6.3
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | Yes, I've heard about this problem... I do not know what a good | solution would be in this case. A special case for gcc 2.95? I am sure | other software projects have this problem too. It would be interesting | to know how it has been fixed. Note that this will also be a problem when the new C standard is out, since it like C++ does not allow implicit return types on functions. The correct solution is for the X(Free) team to correct their header files. Lgb
Re: FYI: Compiling lyx-1.04 with gcc-2.95.1 and X11R6.3
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | Yes, I've heard about this problem... I do not know what a good | solution would be in this case. A special case for gcc 2.95? I am sure | other software projects have this problem too. It would be interesting | to know how it has been fixed. Note that this will also be a problem when the new C standard is out, since it like C++ does not allow implicit return types on functions. The correct solution is for the X(Free) team to correct their header files. Lgb
Re: FYI: Compiling lyx-1.04 with gcc-2.95.1 and X11R6.3
"Svante" == Svante Signell [EMAIL PROTECTED] writes: Svante Hello, I have built the lyx distributions for a long time now Svante using gcc-2.7.2.3. However when compiling lyx-1.0.4 I had Svante upgraded to gcc-2.95.1 and found out that the compiler is VERY Svante picky about type declarations. The compiler did classify Svante undeclared function types in Xlib.h and Xutil.h from the Svante X11R6.3 distribution as errors, not warnings!! The included Svante header files, via forms.h, were treated as C++ header files Svante instead of C header files. Svante The only way I found to solve this was to add the -fpermissive Svante directive to the compiler. Another way which I did later was Svante to edit the header files themseves by replacing all 'extern Svante XFunction' with 'extern int XFunction'. Is this the correct Svante default for undeclared functions in earlier versions of gcc? Svante At least the executable seem to run correctly. Yes, I've heard about this problem... I do not know what a good solution would be in this case. A special case for gcc 2.95? I am sure other software projects have this problem too. It would be interesting to know how it has been fixed. JMarc
Re: FYI: Compiling lyx-1.04 with gcc-2.95.1 and X11R6.3
"Svante" == Svante Signell [EMAIL PROTECTED] writes: Svante Hello, I have built the lyx distributions for a long time now Svante using gcc-2.7.2.3. However when compiling lyx-1.0.4 I had Svante upgraded to gcc-2.95.1 and found out that the compiler is VERY Svante picky about type declarations. The compiler did classify Svante undeclared function types in Xlib.h and Xutil.h from the Svante X11R6.3 distribution as errors, not warnings!! The included Svante header files, via forms.h, were treated as C++ header files Svante instead of C header files. Svante The only way I found to solve this was to add the -fpermissive Svante directive to the compiler. Another way which I did later was Svante to edit the header files themseves by replacing all 'extern Svante XFunction' with 'extern int XFunction'. Is this the correct Svante default for undeclared functions in earlier versions of gcc? Svante At least the executable seem to run correctly. Yes, I've heard about this problem... I do not know what a good solution would be in this case. A special case for gcc 2.95? I am sure other software projects have this problem too. It would be interesting to know how it has been fixed. JMarc
Re: FYI: Compiling lyx-1.04 with gcc-2.95.1 and X11R6.3
> "Svante" == Svante Signell <[EMAIL PROTECTED]> writes: Svante> Hello, I have built the lyx distributions for a long time now Svante> using gcc-2.7.2.3. However when compiling lyx-1.0.4 I had Svante> upgraded to gcc-2.95.1 and found out that the compiler is VERY Svante> picky about type declarations. The compiler did classify Svante> undeclared function types in Xlib.h and Xutil.h from the Svante> X11R6.3 distribution as errors, not warnings!! The included Svante> header files, via forms.h, were treated as C++ header files Svante> instead of C header files. Svante> The only way I found to solve this was to add the -fpermissive Svante> directive to the compiler. Another way which I did later was Svante> to edit the header files themseves by replacing all 'extern Svante> XFunction' with 'extern int XFunction'. Is this the correct Svante> default for undeclared functions in earlier versions of gcc? Svante> At least the executable seem to run correctly. Yes, I've heard about this problem... I do not know what a good solution would be in this case. A special case for gcc 2.95? I am sure other software projects have this problem too. It would be interesting to know how it has been fixed. JMarc
