Re: error compiling latest cvs with-frontend=kde
John Levon [EMAIL PROTECTED] writes: | On 25 Sep 2000, Jean-Marc Lasgouttes wrote: | | "John" == John Levon [EMAIL PROTECTED] writes: | | Anyone any ideas ? Or should I just #define __STRICT_ANSI__ (yuck) | | John and looking further I have found the answer. LyX specifically | John removes this define (and in fact won't compile with it). I | John assume this won't change anytime soon, so I will just have to | John define it temporarily when I include the Qt header. | | I remember we decided to undefine __STRICT_ANSI__ because some code | did not work (some C functions were not defined anymore). What kind of | compile break do you get? We are trying to go towards ANSI | conformance, after all... | | JMarc | | | JMarc, I will investigate exactly what breaks when __STRICT_ANSI__ is | defined later. I would like if possible to leave this defined so we don't | lie to header files ;) And we could also just remove the "-ansi" flag. It isn't doing much for C++ anyway. Lgb
Re: error compiling latest cvs with-frontend=kde
John Levon <[EMAIL PROTECTED]> writes: | On 25 Sep 2000, Jean-Marc Lasgouttes wrote: | | > > "John" == John Levon <[EMAIL PROTECTED]> writes: | > | > >> Anyone any ideas ? Or should I just #define __STRICT_ANSI__ (yuck) | > | > John> and looking further I have found the answer. LyX specifically | > John> removes this define (and in fact won't compile with it). I | > John> assume this won't change anytime soon, so I will just have to | > John> define it temporarily when I include the Qt header. | > | > I remember we decided to undefine __STRICT_ANSI__ because some code | > did not work (some C functions were not defined anymore). What kind of | > compile break do you get? We are trying to go towards ANSI | > conformance, after all... | > | > JMarc | > | | JMarc, I will investigate exactly what breaks when __STRICT_ANSI__ is | defined later. I would like if possible to leave this defined so we don't | lie to header files ;) And we could also just remove the "-ansi" flag. It isn't doing much for C++ anyway. Lgb
Re: error compiling latest cvs with-frontend=kde
"John" == John Levon [EMAIL PROTECTED] writes: Anyone any ideas ? Or should I just #define __STRICT_ANSI__ (yuck) John and looking further I have found the answer. LyX specifically John removes this define (and in fact won't compile with it). I John assume this won't change anytime soon, so I will just have to John define it temporarily when I include the Qt header. I remember we decided to undefine __STRICT_ANSI__ because some code did not work (some C functions were not defined anymore). What kind of compile break do you get? We are trying to go towards ANSI conformance, after all... JMarc
Re: error compiling latest cvs with-frontend=kde
On 25 Sep 2000, Jean-Marc Lasgouttes wrote: "John" == John Levon [EMAIL PROTECTED] writes: Anyone any ideas ? Or should I just #define __STRICT_ANSI__ (yuck) John and looking further I have found the answer. LyX specifically John removes this define (and in fact won't compile with it). I John assume this won't change anytime soon, so I will just have to John define it temporarily when I include the Qt header. I remember we decided to undefine __STRICT_ANSI__ because some code did not work (some C functions were not defined anymore). What kind of compile break do you get? We are trying to go towards ANSI conformance, after all... JMarc JMarc, I will investigate exactly what breaks when __STRICT_ANSI__ is defined later. I would like if possible to leave this defined so we don't lie to header files ;) thanks john p.s. I noticed you weren't certified on advogato yet ! Why haven't you put yourself down as LyX developer ? Do you not use the account at all
Re: error compiling latest cvs with-frontend=kde
"John" == John Levon [EMAIL PROTECTED] writes: John JMarc, I will investigate exactly what breaks when John __STRICT_ANSI__ is defined later. I would like if possible to John leave this defined so we don't lie to header files ;) It would indeed be much better... JMarc
Re: error compiling latest cvs with-frontend=kde
> "John" == John Levon <[EMAIL PROTECTED]> writes: >> Anyone any ideas ? Or should I just #define __STRICT_ANSI__ (yuck) John> and looking further I have found the answer. LyX specifically John> removes this define (and in fact won't compile with it). I John> assume this won't change anytime soon, so I will just have to John> define it temporarily when I include the Qt header. I remember we decided to undefine __STRICT_ANSI__ because some code did not work (some C functions were not defined anymore). What kind of compile break do you get? We are trying to go towards ANSI conformance, after all... JMarc
Re: error compiling latest cvs with-frontend=kde
On 25 Sep 2000, Jean-Marc Lasgouttes wrote: > > "John" == John Levon <[EMAIL PROTECTED]> writes: > > >> Anyone any ideas ? Or should I just #define __STRICT_ANSI__ (yuck) > > John> and looking further I have found the answer. LyX specifically > John> removes this define (and in fact won't compile with it). I > John> assume this won't change anytime soon, so I will just have to > John> define it temporarily when I include the Qt header. > > I remember we decided to undefine __STRICT_ANSI__ because some code > did not work (some C functions were not defined anymore). What kind of > compile break do you get? We are trying to go towards ANSI > conformance, after all... > > JMarc > JMarc, I will investigate exactly what breaks when __STRICT_ANSI__ is defined later. I would like if possible to leave this defined so we don't lie to header files ;) thanks john p.s. I noticed you weren't certified on advogato yet ! Why haven't you put yourself down as LyX developer ? Do you not use the account at all
Re: error compiling latest cvs with-frontend=kde
> "John" == John Levon <[EMAIL PROTECTED]> writes: John> JMarc, I will investigate exactly what breaks when John> __STRICT_ANSI__ is defined later. I would like if possible to John> leave this defined so we don't lie to header files ;) It would indeed be much better... JMarc
Re: error compiling latest cvs with-frontend=kde
On Thu, 21 Sep 2000, John Levon wrote: I have seen this myself. It is to do with Qt breaking by trying to use xor which is a keyword in standard c++. In my opinion this is a broken header used in Qt. For the benefit of the list the relevant section is : #if !(defined(__STRICT_ANSI__) defined(_CC_GNU_)) !defined(_CC_EDG_) !defined(_CC_HP_) !defined(_CC_HP_ACC_) !defined(_CC_USLC_) !defined(_CC_MWERKS_) !defined(xor) QRegion xor( const QRegion ) const; #endif QRegion eor( const QRegion ) const; Does someone want to suggest how this might be worked around ? In my opinion this is Qt being wrong, again. This seems in fact to be a gcc funniness. We have -ansi option used, but it is not defining __STRICT_ANSI__ (as verified via gcc ... -E -dM). Anyone any ideas ? Or should I just #define __STRICT_ANSI__ (yuck) john
Re: error compiling latest cvs with-frontend=kde
On Fri, 22 Sep 2000, John Levon wrote: Anyone any ideas ? Or should I just #define __STRICT_ANSI__ (yuck) john and looking further I have found the answer. LyX specifically removes this define (and in fact won't compile with it). I assume this won't change anytime soon, so I will just have to define it temporarily when I include the Qt header. thanks john what about attached patch ? I really don't like this solution :( -- Oak: Hackers are generally quite happy to use the masculine pronoun as a non-gender-specific reference, as they understand that "fixing" legacy systems is often more troublesome than conforming to their peculiarities. ansi.tar.gz
Re: error compiling latest cvs with-frontend=kde
On Thu, 21 Sep 2000, John Levon wrote: > I have seen this myself. It is to do with Qt breaking by trying to use xor > which is a keyword in standard c++. In my opinion this is a broken header > used in Qt. For the benefit of the list the relevant section is : > > #if !(defined(__STRICT_ANSI__) && defined(_CC_GNU_)) && !defined(_CC_EDG_) > && !defined(_CC_HP_) && !defined(_CC_HP_ACC_) && !defined(_CC_USLC_) && > !defined(_CC_MWERKS_) && !defined(xor) > QRegion xor( const QRegion & ) const; > #endif > QRegion eor( const QRegion & ) const; > > > Does someone want to suggest how this might be worked around ? In my > opinion this is Qt being wrong, again. > This seems in fact to be a gcc funniness. We have -ansi option used, but it is not defining __STRICT_ANSI__ (as verified via gcc ... -E -dM). Anyone any ideas ? Or should I just #define __STRICT_ANSI__ (yuck) john
Re: error compiling latest cvs with-frontend=kde
On Fri, 22 Sep 2000, John Levon wrote: > Anyone any ideas ? Or should I just #define __STRICT_ANSI__ (yuck) > > john > and looking further I have found the answer. LyX specifically removes this define (and in fact won't compile with it). I assume this won't change anytime soon, so I will just have to define it temporarily when I include the Qt header. thanks john what about attached patch ? I really don't like this solution :( -- Oak: Hackers are generally quite happy to use the masculine pronoun as a non-gender-specific reference, as they understand that "fixing" legacy systems is often more troublesome than conforming to their peculiarities. ansi.tar.gz
error compiling latest cvs with-frontend=kde
When compiling lyx-devel, cvs sep 21, on a redhat 6.2 system, with qt1x-1.45-3 qt1x-devel-1.45-3[ gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) and doing ./configure --disable-nls --with-frontend=kde --with-qt-dir=/usr/lib/qt-1.45 I get the following error message: /bin/sh ../../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../../../src -I../../../src/ -I../../../src/frontends/-I../../.. -I../../.. -I./kde -I/usr/lib/qt-1.45/include -I/usr/include/kde -I../../../src/frontends/xforms -isystem /usr/X11R6/include -g -O -fno-rtti -fno-exceptions -ansi -W -Wall -Wno-return-type -c FormToc.C g++ -DHAVE_CONFIG_H -I. -I. -I../../../src -I../../../src/ -I../../../src/frontends/ -I../../.. -I../../.. -I./kde -I/usr/lib/qt-1.45/include -I/usr/include/kde -I../../../src/frontends/xforms -isystem /usr/X11R6/include -g -O -fno-rtti -fno-exceptions -ansi -W -Wall -Wno-return-type -Wp,-MD,.deps/FormToc.pp -c FormToc.C -o FormToc.o In file included from /usr/lib/qt-1.45/include/qpainter.h:33, from /usr/lib/qt-1.45/include/qdrawutil.h:28, from /usr/lib/qt-1.45/include/qscrollbar.h:30, from /usr/lib/qt-1.45/include/qscrollview.h:28, from /usr/lib/qt-1.45/include/qlistview.h:37, from formtocdialog.h:28, from FormToc.C:20: /usr/lib/qt-1.45/include/qregion.h:74: parse error before `^' /usr/lib/qt-1.45/include/qregion.h:118: duplicate nested type `QRegion' make[4]: *** [FormToc.lo] Error 1 make[4]: Leaving directory `/tmp/lyx-devel/src/frontends/kde' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/tmp/lyx-devel/src/frontends' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/lyx-devel/src' make[1]: *** [all-recursive-am] Error 2 make[1]: Leaving directory `/tmp/lyx-devel/src' make: *** [all-recursive] Error 1 Edwin
Re: error compiling latest cvs with-frontend=kde
On Thu, 21 Sep 2000, Edwin Leuven wrote: I get the following error message: /bin/sh ../../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../../../src -I../../../src/ -I../../../src/frontends/-I../../.. -I../../.. -I./kde -I/usr/lib/qt-1.45/include -I/usr/include/kde -I../../../src/frontends/xforms -isystem /usr/X11R6/include -g -O -fno-rtti -fno-exceptions -ansi -W -Wall -Wno-return-type -c FormToc.C g++ -DHAVE_CONFIG_H -I. -I. -I../../../src -I../../../src/ -I../../../src/frontends/ -I../../.. -I../../.. -I./kde -I/usr/lib/qt-1.45/include -I/usr/include/kde -I../../../src/frontends/xforms -isystem /usr/X11R6/include -g -O -fno-rtti -fno-exceptions -ansi -W -Wall -Wno-return-type -Wp,-MD,.deps/FormToc.pp -c FormToc.C -o FormToc.o In file included from /usr/lib/qt-1.45/include/qpainter.h:33, from /usr/lib/qt-1.45/include/qdrawutil.h:28, from /usr/lib/qt-1.45/include/qscrollbar.h:30, from /usr/lib/qt-1.45/include/qscrollview.h:28, from /usr/lib/qt-1.45/include/qlistview.h:37, from formtocdialog.h:28, from FormToc.C:20: /usr/lib/qt-1.45/include/qregion.h:74: parse error before `^' /usr/lib/qt-1.45/include/qregion.h:118: duplicate nested type `QRegion' make[4]: *** [FormToc.lo] Error 1 make[4]: Leaving directory `/tmp/lyx-devel/src/frontends/kde' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/tmp/lyx-devel/src/frontends' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/lyx-devel/src' make[1]: *** [all-recursive-am] Error 2 make[1]: Leaving directory `/tmp/lyx-devel/src' make: *** [all-recursive] Error 1 Edwin I have seen this myself. It is to do with Qt breaking by trying to use xor which is a keyword in standard c++. In my opinion this is a broken header used in Qt. For the benefit of the list the relevant section is : #if !(defined(__STRICT_ANSI__) defined(_CC_GNU_)) !defined(_CC_EDG_) !defined(_CC_HP_) !defined(_CC_HP_ACC_) !defined(_CC_USLC_) !defined(_CC_MWERKS_) !defined(xor) QRegion xor( const QRegion ) const; #endif QRegion eor( const QRegion ) const; Does someone want to suggest how this might be worked around ? In my opinion this is Qt being wrong, again. thanks john p.s. Edwin, you may temporarily work around this by commenting out line 74 of /usr/lib/qt-1.45/include/qregion.h by placing // in front of it. Otherwise you can wait till a fix is in place.
error compiling latest cvs with-frontend=kde
When compiling lyx-devel, cvs sep 21, on a redhat 6.2 system, with qt1x-1.45-3 qt1x-devel-1.45-3[ gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) and doing ./configure --disable-nls --with-frontend=kde --with-qt-dir=/usr/lib/qt-1.45 I get the following error message: /bin/sh ../../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../../../src -I../../../src/ -I../../../src/frontends/-I../../.. -I../../.. -I./kde -I/usr/lib/qt-1.45/include -I/usr/include/kde -I../../../src/frontends/xforms -isystem /usr/X11R6/include -g -O -fno-rtti -fno-exceptions -ansi -W -Wall -Wno-return-type -c FormToc.C g++ -DHAVE_CONFIG_H -I. -I. -I../../../src -I../../../src/ -I../../../src/frontends/ -I../../.. -I../../.. -I./kde -I/usr/lib/qt-1.45/include -I/usr/include/kde -I../../../src/frontends/xforms -isystem /usr/X11R6/include -g -O -fno-rtti -fno-exceptions -ansi -W -Wall -Wno-return-type -Wp,-MD,.deps/FormToc.pp -c FormToc.C -o FormToc.o In file included from /usr/lib/qt-1.45/include/qpainter.h:33, from /usr/lib/qt-1.45/include/qdrawutil.h:28, from /usr/lib/qt-1.45/include/qscrollbar.h:30, from /usr/lib/qt-1.45/include/qscrollview.h:28, from /usr/lib/qt-1.45/include/qlistview.h:37, from formtocdialog.h:28, from FormToc.C:20: /usr/lib/qt-1.45/include/qregion.h:74: parse error before `^' /usr/lib/qt-1.45/include/qregion.h:118: duplicate nested type `QRegion' make[4]: *** [FormToc.lo] Error 1 make[4]: Leaving directory `/tmp/lyx-devel/src/frontends/kde' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/tmp/lyx-devel/src/frontends' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/lyx-devel/src' make[1]: *** [all-recursive-am] Error 2 make[1]: Leaving directory `/tmp/lyx-devel/src' make: *** [all-recursive] Error 1 Edwin
Re: error compiling latest cvs with-frontend=kde
On Thu, 21 Sep 2000, Edwin Leuven wrote: > I get the following error message: > /bin/sh ../../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../../../src >-I../../../src/ -I../../../src/frontends/-I../../.. -I../../.. -I./kde >-I/usr/lib/qt-1.45/include -I/usr/include/kde -I../../../src/frontends/xforms >-isystem /usr/X11R6/include -g -O -fno-rtti -fno-exceptions -ansi -W -Wall >-Wno-return-type -c FormToc.C > g++ -DHAVE_CONFIG_H -I. -I. -I../../../src -I../../../src/ -I../../../src/frontends/ >-I../../.. -I../../.. -I./kde -I/usr/lib/qt-1.45/include -I/usr/include/kde >-I../../../src/frontends/xforms -isystem /usr/X11R6/include -g -O -fno-rtti >-fno-exceptions -ansi -W -Wall -Wno-return-type -Wp,-MD,.deps/FormToc.pp -c FormToc.C >-o FormToc.o > In file included from /usr/lib/qt-1.45/include/qpainter.h:33, > from /usr/lib/qt-1.45/include/qdrawutil.h:28, > from /usr/lib/qt-1.45/include/qscrollbar.h:30, > from /usr/lib/qt-1.45/include/qscrollview.h:28, > from /usr/lib/qt-1.45/include/qlistview.h:37, > from formtocdialog.h:28, > from FormToc.C:20: > /usr/lib/qt-1.45/include/qregion.h:74: parse error before `^' > /usr/lib/qt-1.45/include/qregion.h:118: duplicate nested type `QRegion' > make[4]: *** [FormToc.lo] Error 1 > make[4]: Leaving directory `/tmp/lyx-devel/src/frontends/kde' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory `/tmp/lyx-devel/src/frontends' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/tmp/lyx-devel/src' > make[1]: *** [all-recursive-am] Error 2 > make[1]: Leaving directory `/tmp/lyx-devel/src' > make: *** [all-recursive] Error 1 > > > Edwin > I have seen this myself. It is to do with Qt breaking by trying to use xor which is a keyword in standard c++. In my opinion this is a broken header used in Qt. For the benefit of the list the relevant section is : #if !(defined(__STRICT_ANSI__) && defined(_CC_GNU_)) && !defined(_CC_EDG_) && !defined(_CC_HP_) && !defined(_CC_HP_ACC_) && !defined(_CC_USLC_) && !defined(_CC_MWERKS_) && !defined(xor) QRegion xor( const QRegion & ) const; #endif QRegion eor( const QRegion & ) const; Does someone want to suggest how this might be worked around ? In my opinion this is Qt being wrong, again. thanks john p.s. Edwin, you may temporarily work around this by commenting out line 74 of /usr/lib/qt-1.45/include/qregion.h by placing // in front of it. Otherwise you can wait till a fix is in place.
