Re: [automated testing] debian testing: compile failure with qt6

On Sat, 10 May 2025 at 08:55, José Matos wrote: > On Sat, 2025-05-10 at 01:34 +, test...@tester.lyx.org wrote: > > insets/InsetFloat.cpp:376:1: error: control reaches end of non-void > function > > FWIW that is the only warning. > > I am not sure if using -Werror=return-type fails after the f

Re: [automated testing] debian testing: compile failure with qt6

On Sat, 2025-05-10 at 01:34 +, test...@tester.lyx.org wrote: > insets/InsetFloat.cpp:376:1: error: control reaches end of non-void function FWIW that is the only warning. I am not sure if using -Werror=return-type fails after the first warning or not. :-) Regards, -- José Abílio -- lyx-dev

[automated testing] debian testing: compile failure with qt6

Making all in autotests Making all in config Making all in development Making all in po Making all in 3rdparty Making all in nod Making all in src CHK lyx_commit_hash.h Making all in support Making all in frontends Making all in qt Making all in . Making all in . CHK lyx_commit_hash.h

Re: [automated testing] bionic: compile failure

Am Sonntag, dem 06.04.2025 um 12:58 +0200 schrieb Kornel Benko: > > GuiPrefs.cpp: In member function 'void > > lyx::frontend::PrefColors::initializeColorsTV()': > > GuiPrefs.cpp:1716:25: error: 'class QFontMetrics' has no member > > named > > 'horizontalAdvance' int col_width = > > max(fm.horizonta

Re: [automated testing] bionic: compile failure

On Sun, Apr 06, 2025 at 12:58:20PM +0200, Kornel Benko wrote: > Am Sun, 6 Apr 2025 10:27:42 + > schrieb test...@tester.lyx.org: > > > Making all in autotests > > Making all in config > > Making all in development > > Making all in po > > Making all in 3rdparty > > Making all in nod > > Making

Re: [automated testing] bionic: compile failure

Am Sun, 6 Apr 2025 10:27:42 + schrieb test...@tester.lyx.org: > Making all in autotests > Making all in config > Making all in development > Making all in po > Making all in 3rdparty > Making all in nod > Making all in src > CHK lyx_commit_hash.h > Making all in support > Making all in

[automated testing] bionic: compile failure

Making all in autotests Making all in config Making all in development Making all in po Making all in 3rdparty Making all in nod Making all in src CHK lyx_commit_hash.h Making all in support Making all in frontends Making all in qt CXX GuiPrefs.o GuiPrefs.cpp: In member function 'void

Re: [automated testing] bionic: compile failure

Le 18/03/2025 à 10:07, test...@tester.lyx.org a écrit : Making all in autotests Making all in config Making all in development Making all in po Making all in 3rdparty Making all in nod Making all in src CHK lyx_commit_hash.h Making all in support Making all in frontends Making all in qt

[automated testing] bionic: compile failure

Making all in autotests Making all in config Making all in development Making all in po Making all in 3rdparty Making all in nod Making all in src CHK lyx_commit_hash.h Making all in support Making all in frontends Making all in qt CXX GuiPrefs.o GuiPrefs.cpp: In member function 'virt

[automated testing] bionic: compile failure

Making all in autotests Making all in config Making all in development Making all in po Making all in 3rdparty Making all in nod Making all in src CHK lyx_commit_hash.h Making all in support Making all in frontends Making all in qt CXX GuiView.o GuiView.cpp: In member function 'void

[automated testing] debian testing: compile failure with qt6

Making all in autotests Making all in config Making all in development Making all in po Making all in 3rdparty Making all in nod Making all in src CHK lyx_commit_hash.h Making all in support Making all in frontends Making all in qt CXX DialogFactory.o In file included from GuiPrefs.h:

[automated testing] bionic: compile failure

Making all in autotests Making all in config Making all in development Making all in po Making all in 3rdparty Making all in nod Making all in src CHK lyx_commit_hash.h Making all in support Making all in frontends Making all in qt CXX DialogFactory.o In file included from GuiPrefs.h:

[automated testing] debian testing: compile failure with qt6

Making all in autotests Making all in config Making all in development Making all in po Making all in 3rdparty Making all in nod Making all in src CHK lyx_commit_hash.h Making all in support Making all in frontends Making all in qt CXX GuiPrefs.o GuiPrefs.cpp: In constructor 'lyx::fr

[automated testing] bionic: compile failure

Making all in autotests Making all in config Making all in development Making all in po Making all in 3rdparty Making all in nod Making all in src CHK lyx_commit_hash.h Making all in support Making all in frontends Making all in qt CXX DialogFactory.o In file included from GuiPrefs.h:

Re: [automated testing] debian testing: compile failure with qt6

Le 6 février 2025 23:45:08 GMT+01:00, Thibaut Cuvelier a écrit : > >I implemented this suggestion (it required a bit of ground work due to the >places this function is used) in 87f08ce2. Thanks. >I bet this compilation error is a compiler difference: MSVC didn't complain >at all about the mis

Re: [automated testing] debian testing: compile failure with qt6

On Thu, 6 Feb 2025 at 12:53, Jean-Marc Lasgouttes wrote: > Le 06/02/2025 à 12:19, Scott Kostyshak a écrit : > >> mathed/InsetMathSymbol.cpp: In member function 'virtual void > lyx::InsetMathSymbol::mathmlize(lyx::MathMLStream&) const': > >> mathed/InsetMathSymbol.cpp:167:20: error: 'strcmp' was n

Re: [automated testing] debian testing: compile failure with qt6

Le 06/02/2025 à 12:19, Scott Kostyshak a écrit : mathed/InsetMathSymbol.cpp: In member function 'virtual void lyx::InsetMathSymbol::mathmlize(lyx::MathMLStream&) const': mathed/InsetMathSymbol.cpp:167:20: error: 'strcmp' was not declared in this scope 167 | } else if (strcmp(sym_->Ma

Re: [automated testing] debian testing: compile failure with qt6

On Thu, Feb 06, 2025 at 02:16:35AM +, test...@tester.lyx.org wrote: > Making all in autotests > Making all in config > Making all in development > Making all in po > Making all in 3rdparty > Making all in nod > Making all in src > CHK lyx_commit_hash.h > Making all in support > Making al

[automated testing] debian testing: compile failure with qt6

Making all in autotests Making all in config Making all in development Making all in po Making all in 3rdparty Making all in nod Making all in src CHK lyx_commit_hash.h Making all in support Making all in frontends Making all in qt Making all in . Making all in . CHK lyx_commit_hash.h

Re: [ci announce] bionic: compile failure

On Fri, Jan 24, 2025 at 03:33:27PM +0100, Jean-Marc Lasgouttes wrote: > Le 24/01/2025 à 14:51, Scott Kostyshak a écrit : > > > I don't know, [automated testing] for example ? > > > > Just to propose something different: [compilation tests, gcc A.B.B, Qt X.ZY] > > > > Or if it's easier, dump gcc -

Re: [ci announce] bionic: compile failure

Le 24/01/2025 à 14:51, Scott Kostyshak a écrit : I don't know, [automated testing] for example ? Just to propose something different: [compilation tests, gcc A.B.B, Qt X.ZY] Or if it's easier, dump gcc --version and the Qt version into the message body? But I know that's verbose and don't min

Re: [ci announce] bionic: compile failure

On Fri, Jan 24, 2025 at 02:40:30PM +0100, Jean-Marc Lasgouttes wrote: > Le 24/01/2025 à 14:36, Pavel Sanda a écrit : > > On Fri, Jan 24, 2025 at 02:18:30PM +0100, Jean-Marc Lasgouttes wrote: > > > Would it be possible to use "make -s" to make the reports less wordy, and > > > maybe to change the me

Re: [ci announce] bionic: compile failure

Le 24/01/2025 à 14:36, Pavel Sanda a écrit : On Fri, Jan 24, 2025 at 02:18:30PM +0100, Jean-Marc Lasgouttes wrote: Would it be possible to use "make -s" to make the reports less wordy, and maybe to change the message title ? [ci announce] is weird. No problem, what is your favorite title? I

Re: [ci announce] bionic: compile failure

On Fri, Jan 24, 2025 at 02:18:30PM +0100, Jean-Marc Lasgouttes wrote: > Would it be possible to use "make -s" to make the reports less wordy, and > maybe to change the message title ? [ci announce] is weird. No problem, what is your favorite title? Pavel -- lyx-devel mailing list lyx-devel@lists

Re: [ci announce] bionic: compile failure

Le 24/01/2025 à 09:13, Jürgen Spitzmüller a écrit : Am Donnerstag, dem 23.01.2025 um 22:42 + schrieb test...@tester.lyx.org: GuiInputMethod.cpp: In member function 'std::array lyx::frontend::GuiInputMethod::setCaretOffset(lyx::pos_type)': GuiInputMethod.cpp:551:26: error: 'class QFontMetrics

Re: [ci announce] bionic: compile failure

Am Donnerstag, dem 23.01.2025 um 22:42 + schrieb test...@tester.lyx.org: > GuiInputMethod.cpp: In member function 'std::array > lyx::frontend::GuiInputMethod::setCaretOffset(lyx::pos_type)': > GuiInputMethod.cpp:551:26: error: 'class QFontMetrics' has no member > named 'horizontalAdvance' >    

[ci announce] bionic: compile failure

make all-recursive make[1]: Entering directory '/home/lyx/lyx' Making all in autotests make[2]: Entering directory '/home/lyx/lyx/autotests' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/home/lyx/lyx/autotests' Making all in config make[2]: Entering directory '/home/lyx/lyx/c

Re: Current trunk compile failure with lyxfind.cpp

On Tue, Feb 8, 2011 at 4:18 AM, Tommaso Cucinotta wrote: > Il 08/02/2011 03:42, BH ha scritto: >> >> On Mac, using cmake, I can't compile: >> >> Building CXX object >> src/CMakeFiles/LyX.dir/Users/bennett/lyx/lyx-devel/src/lyxfind.cpp.o >> /Users/bennett/lyx/lyx-devel/src/lyxfind.cpp: In function

Re: Current trunk compile failure with lyxfind.cpp

Il 08/02/2011 03:42, BH ha scritto: On Mac, using cmake, I can't compile: Building CXX object src/CMakeFiles/LyX.dir/Users/bennett/lyx/lyx-devel/src/lyxfind.cpp.o /Users/bennett/lyx/lyx-devel/src/lyxfind.cpp: In function ‘int lyxfindForwardAdv(lyx::DocIterator&, lyxMatchStringAdv&)’: /Us

Current trunk compile failure with lyxfind.cpp

On Mac, using cmake, I can't compile: Building CXX object src/CMakeFiles/LyX.dir/Users/bennett/lyx/lyx-devel/src/lyxfind.cpp.o /Users/bennett/lyx/lyx-devel/src/lyxfind.cpp: In function ‘int lyxfindForwardAdv(lyx::DocIterator&, lyxMatchStringAdv&)’: /Users/bennett/lyx/lyx-devel/src/lyxfind.

Re: r25238 compile failure

On Thu, Jun 12, 2008 at 1:34 PM, Abdelrazak Younes <[EMAIL PROTECTED]> wrote: > Should be fixed now. Yep -- and the bug is fixed, too. Thanks! Bennett

Re: r25238 compile failure

Should be fixed now. Abdel.

r25238 compile failure

if /bin/sh ../../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -DQT_NO_STL -DQT_NO_KEYWORDS -I../../../src -I../../../src/frontends -I../../../images -I/Users/bennett/lyx/qt-4.4-install/include -I/Users/bennett/lyx/qt-4.4-install/include/QtGui -I/Users/bennett/lyx/qt-4

Re: compile failure today: No rule to make target `ui_IndexUi.h'

> I ran autogen.sh, make distclean, configure, make, and got this. > The file ui_IndexUi.h does indeed not exist on my machine. i usually run autogen.sh after make distclean. fresh checkout does not help? pavel

compile failure today: No rule to make target `ui_IndexUi.h'

I ran autogen.sh, make distclean, configure, make, and got this. The file ui_IndexUi.h does indeed not exist on my machine. Helge Hafting

Re: Compile failure

Pavel Sanda wrote: > fix attached. Thanks. Committed. Jürgen

Re: Compile failure

> fix attached. eh, wrong file name. pavel --- index.php 2007-11-05 09:41:18.0 +0100 +++ pg.new 2007-11-05 09:32:52.0 +0100 @@ -116,7 +152,7 @@ If you have a question regarding the development of LyX, please write us at the -LyX +LyX developers' mailing list. Thanks f

Re: Compile failure

> BTW, the link on http://www.lyx.org/devel to the LyX developers mailing > list on the LyX site is broken > (http://www.lyx.org/devel/internet/mailing.php#lyx-devel). Where is the > main page for the mailing list? http://www.lyx.org/internet/mailing.php#lyx-devel fix attached. pavel --- p

Re: Compile failure

On Nov 4, 2007, at 9:18 PM, Bennett Helm wrote: I'm also using Qt-4.3.1; I don't know if that would make a difference. I'll try compiling Qt-4.3.2 to see what happens. Qt-4.3.2 works fine for me. One question: did you set LDFLAGS? Yup. As per the instructions in INSTALL.MacOSX, I used: e

Re: Compile failure

On Nov 4, 2007, at 9:18 PM, Bennett Helm wrote: I'm also using Qt-4.3.1; I don't know if that would make a difference. I'll try compiling Qt-4.3.2 to see what happens. Qt-4.3.2 works fine for me. One question: did you set LDFLAGS? As a last resort, try: make clean ... reconfigure ... make.

Re: Compile failure

[Switching this over to the devel list] On Nov 4, 2007, at 2:19 PM, Christopher Menzel wrote: On Nov 4, 2007, at 11:16 AM, Pavel Sanda wrote: Yes, a good suggesetion, but the curious thing is that I am setting it. whats the exact configure command you use ? For compiling Qt: ./config

compile failure: current trunk

On Mac, I get the following error: Making all in qt4 /Users/bennett/lyx/qt-4.3-install///bin/moc -o DialogView_moc.cpp DialogView.h DialogView.h:0: Warning: No relevant classes found. No output generated. /Users/bennett/lyx/qt-4.3-install///bin/moc -o DockView_moc.cpp DockView.h DockView.h:

Re: Compile failure: No rule to make target `all'

On Wed, Sep 26, 2007 at 01:37:29AM +0200, Pavel Sanda wrote: > > > So I can't make 'all' in po/ ? :-( > > > > Does the attached patch help? > > yes, it does. can you put it in trunk ? I committed it. -- Enrico

Re: Compile failure: No rule to make target `all'

> > So I can't make 'all' in po/ ? :-( > > Does the attached patch help? yes, it does. can you put it in trunk ? pavel

Re: Compile failure: No rule to make target `all'

On Mon, Sep 24, 2007 at 10:40:53PM +0200, Helge Hafting wrote: > I gave up - a hang during a compile really screwed up things. > > So I downloaded everything from svn again. > Ran autogen.sh and configure. > > Then: > $ make > Making all in config > make[1]: Entering directory `/usr/src/lyx-devel

Re: Compile failure: No rule to make target `all'

I gave up - a hang during a compile really screwed up things. So I downloaded everything from svn again. Ran autogen.sh and configure. Then: $ make Making all in config make[1]: Entering directory `/usr/src/lyx-devel/config' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr

Re: Compile failure 1.6 svn, missing FloatList.cpp

On Mon, Sep 24, 2007 at 06:02:40AM +0300, Martin Vermeer wrote: > On Mon, Sep 24, 2007 at 12:09:07AM +0200, Helge Hafting wrote: > > make[1]: Entering directory `/usr/src/lyx-devel/src/tex2lyx' > > make PCH_FLAGS= pch-file > > make[2]: Entering directory `/usr/src/lyx-devel/src/tex2lyx' > > g++ -DH

Re: Compile failure 1.6 svn, missing FloatList.cpp

On Mon, Sep 24, 2007 at 12:09:07AM +0200, Helge Hafting wrote: > make[1]: Entering directory `/usr/src/lyx-devel/src/tex2lyx' > make PCH_FLAGS= pch-file > make[2]: Entering directory `/usr/src/lyx-devel/src/tex2lyx' > g++ -DHAVE_CONFIG_H -DTEX2LYX -I../../src/tex2lyx -I../../src > -I../../src

Compile failure 1.6 svn, missing FloatList.cpp

make[1]: Entering directory `/usr/src/lyx-devel/src/tex2lyx' make PCH_FLAGS= pch-file make[2]: Entering directory `/usr/src/lyx-devel/src/tex2lyx' g++ -DHAVE_CONFIG_H -DTEX2LYX -I../../src/tex2lyx -I../../src -I../../src -Wextra -Wall -g -Os -x c++-header -fPIC -DPIC ./pch.h -o ./pch.h.g

Compile failure on Mac

With 1.6, I get the following compile failure. /bin/sh ../../../libtool --tag=CXX --mode=compile g++ - DHAVE_CONFIG_H -I. -I../../../src -I../../../src -I../../../boost - Wextra -Wall -I/System/Library/Frameworks/CoreFoundation.framework/ Headers -g -Os -MT ControlEmbeddedFiles.lo -MD

Re: Compile failure

On Mar 25, 2007, at 9:53 AM, Abdelrazak Younes wrote: Georg Baum wrote: Am Sonntag, 25. März 2007 15:25 schrieb Abdelrazak Younes: Is there a more general problem WRT enum forward declaration in gcc? Or in the standard? The latter. Forward declaring enums is not possible, since the compiler

Re: Compile failure

Georg Baum wrote: Am Sonntag, 25. März 2007 15:25 schrieb Abdelrazak Younes: Is there a more general problem WRT enum forward declaration in gcc? Or in the standard? The latter. Forward declaring enums is not possible, since the compiler needs to know the definition of the enum in order to d

Re: Compile failure

Am Sonntag, 25. März 2007 15:25 schrieb Abdelrazak Younes: > Is there a more general problem WRT enum forward declaration in gcc? Or > in the standard? The latter. Forward declaring enums is not possible, since the compiler needs to know the definition of the enum in order to determine it's siz

Re: Compile failure

Edwin Leuven wrote: Suggestions? missing include? I don't think this is the reason... Bennett's compiler is complaining about the forward declaration of lyx::biblio::CiteEngine (which is declared in biblio.h). Is there a more general problem WRT enum forward declaration in gcc? Or in the s

Re: Compile failure

Suggestions? missing include? Index: src/bufferparams.h === --- src/bufferparams.h (revision 17540) +++ src/bufferparams.h (working copy) @@ -19,10 +19,12 @@ #include "paper.h" #include "insets/insetquotes.h" +#include "insets/i

Re: Compile failure

Suggestions? I have the same problem here, which makes me unable to accept Abdel's gift about viewsource dialog. :-) Bo

Compile failure

With current svn (17539), I get the following: make all-recursive Making all in mathed make all-am /bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H - I. -I../../src -Winvalid-pch --include=./pch.h -I./.. -I../../boost - Wextra -Wall-g -Os -MT InsetMathCases.lo -MD -MP

Re: 1.5 compile failure on PPC Mac

Bennett Helm <[EMAIL PROTECTED]> writes: | I'm finally getting around to trying to compile 1.5 on PPC Mac, and | I'm running into the following problem (see below). | | The archives suggest that the problem is that Qt-4 is not installed | (though ./configure does not complain): | |

1.5 compile failure on PPC Mac

I'm finally getting around to trying to compile 1.5 on PPC Mac, and I'm running into the following problem (see below). The archives suggest that the problem is that Qt-4 is not installed (though ./configure does not complain):

Compile failure qfont_metrics

qfont_metrics.C: In function 'int::smallcapswidth(const QString&, const LyXFont&)': qfont_metrics.C:50: error: ambiguous overload for 'operator[]' in 's[i]' /usr/include/QtCore/qstring.h:544: note: candidates are: const QChar QString::operator[](int) const /usr/include/QtCore/qstring.h:693: note:

Re: qt4 compile failure

Juergen Spitzmueller wrote: Georg Baum wrote: It took me a while to tell pkg-config where all the qt4 stuff is... I'm recompiling tomorrow. So I did. It turned out that it compiled now without Abdel's fix. Sorry, Abdel! Don't be sorry. You compile problem indirectly told me that there was a

Re: qt4 compile failure

Georg Baum wrote: > > It took me a while to tell pkg-config where all the qt4 stuff is... I'm > > recompiling tomorrow. So I did. It turned out that it compiled now without Abdel's fix. Sorry, Abdel! > Why do you need to? pkg-config finds qt4 out of the box even on my old SuSE > 9.3 machine. AFA

Re: qt4 compile failure

Am Donnerstag, 17. August 2006 21:13 schrieb Juergen Spitzmueller: > It took me a while to tell pkg-config where all the qt4 stuff is... I'm > recompiling tomorrow. Why do you need to? pkg-config finds qt4 out of the box even on my old SuSE 9.3 machine. AFAIK you are using 10.0 or 10.1, could i

Re: qt4 compile failure

Georg Baum wrote: > Am Donnerstag, 17. August 2006 18:38 schrieb Juergen Spitzmueller: > > Abdelrazak Younes wrote: > > > I am wondering, did you configure before running make Juergen? > > > > Yes (no autogen.sh, though). > > Then you still compile with QT3_SUPPORT. Could you undo Abdel's change an

Re: qt4 compile failure

Georg Baum wrote: Am Donnerstag, 17. August 2006 18:47 schrieb Abdelrazak Younes: That explains why gcc gives you the two ctor choices then because I modified qt4.m4 and AFAIK, this is run by autogen.sh, isn't it? Yes. But that does not explain why the KeyboardModifier conversion is not auto

Re: qt4 compile failure

Am Donnerstag, 17. August 2006 18:47 schrieb Abdelrazak Younes: > That explains why gcc gives you the two ctor choices then because I > modified qt4.m4 and AFAIK, this is run by autogen.sh, isn't it? Yes. > But that does not explain why the KeyboardModifier conversion is not > automatically don

Re: qt4 compile failure

Am Donnerstag, 17. August 2006 18:38 schrieb Juergen Spitzmueller: > Abdelrazak Younes wrote: > > I am wondering, did you configure before running make Juergen? > > Yes (no autogen.sh, though). Then you still compile with QT3_SUPPORT. Could you undo Abdel's change and try again after running aut

Re: qt4 compile failure

Am Donnerstag, 17. August 2006 18:35 schrieb Abdelrazak Younes: > Georg Baum wrote: > > Abdelrazak Younes wrote: > > > >> There are default value. > > > > Also in Jürgen's case? > > I guess so as it was fixed by my last patch. Yes, I saw that message only later. Georg

Re: qt4 compile failure

Juergen Spitzmueller wrote: Abdelrazak Younes wrote: I am wondering, did you configure before running make Juergen? Yes (no autogen.sh, though). That explains why gcc gives you the two ctor choices then because I modified qt4.m4 and AFAIK, this is run by autogen.sh, isn't it? But that doe

Re: qt4 compile failure

Abdelrazak Younes wrote: > I am wondering, did you configure before running make Juergen? Yes (no autogen.sh, though). Jürgen

Re: qt4 compile failure

Georg Baum wrote: Abdelrazak Younes wrote: There are default value. Also in Jürgen's case? I guess so as it was fixed by my last patch. Here is the one unique prototype: QKeyEvent ( Type type, int key, Qt::KeyboardModifiers modifiers, const QString & text = QString(), bool autorep = fal

Re: qt4 compile failure

Abdelrazak Younes wrote: > There are default value. Also in Jürgen's case? Georg

Re: qt4 compile failure

Abdelrazak Younes wrote: > My Qt > (4.1.3 win/msvc2005) do automatically the conversion... What is your > version Juergen? 4.1.2 Jürgen

Re: qt4 compile failure

Abdelrazak Younes <[EMAIL PROTECTED]> writes: | > | | Index: GuiWorkArea.C | > | === | > | --- GuiWorkArea.C (revision 14773) | > | +++ GuiWorkArea.C (working copy) | > | @@ -593,7 +593,8 @@ | > | // ideally, such special co

Re: qt4 compile failure

Lars Gullik Bjønnes wrote: [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes: | Abdelrazak Younes <[EMAIL PROTECTED]> writes: | | | Juergen Spitzmueller wrote: | | > Abdelrazak Younes wrote: | | >> Could you try this patch please? | | > Doesn't help. Still the same error. | | | | What about thi

Re: qt4 compile failure

Lars Gullik Bjønnes wrote: Abdelrazak Younes <[EMAIL PROTECTED]> writes: | Juergen Spitzmueller wrote: | > Abdelrazak Younes wrote: | >> Could you try this patch please? | > Doesn't help. Still the same error. | | What about this one? | | Index: GuiWorkArea.C | ==

Re: qt4 compile failure

Georg Baum wrote: Abdelrazak Younes wrote: What about this one? Will probably not work. Look at at the number of arguments in the error message. There are default value. Abdel

Re: qt4 compile failure

[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes: | Abdelrazak Younes <[EMAIL PROTECTED]> writes: | | | Juergen Spitzmueller wrote: | | > Abdelrazak Younes wrote: | | >> Could you try this patch please? | | > Doesn't help. Still the same error. | | | | What about this one? Svn compiles for me wi

Re: qt4 compile failure

Abdelrazak Younes <[EMAIL PROTECTED]> writes: | Juergen Spitzmueller wrote: | > Abdelrazak Younes wrote: | >> Could you try this patch please? | > Doesn't help. Still the same error. | | What about this one? | | Index: GuiWorkArea.C |

Re: qt4 compile failure

Abdelrazak Younes wrote: > What about this one? This one compiles. Jürgen

Re: qt4 compile failure

Abdelrazak Younes wrote: > What about this one? Will probably not work. Look at at the number of arguments in the error message. Georg

Re: qt4 compile failure

Juergen Spitzmueller wrote: Abdelrazak Younes wrote: Could you try this patch please? Doesn't help. Still the same error. What about this one? Index: GuiWorkArea.C === --- GuiWorkArea.C (revision 14773) +++ GuiWorkArea.C

Re: qt4 compile failure

Abdelrazak Younes wrote: > Could you try this patch please? Doesn't help. Still the same error. Jürgen GuiWorkArea.C: In member function 'virtual void lyx::frontend::GuiWorkArea::inputMethodEvent(QInputMethodEvent*)': GuiWorkArea.C:596: error: call of overloaded 'QKeyEvent(QEvent::Type, int&,

Re: qt4 compile failure

Juergen Spitzmueller wrote: gcc-4.1.0, SuSE 10.1 Regards, Jürgen Could you try this patch please? Index: GuiWorkArea.C === --- GuiWorkArea.C (revision 14773) +++ GuiWorkArea.C (working copy) @@ -593,7 +593,7 @@

qt4 compile failure

gcc-4.1.0, SuSE 10.1 Regards, Jürgen GuiWorkArea.C: In member function 'virtual void lyx::frontend::GuiWorkArea::inputMethodEvent(QInputMethodEvent*)': GuiWorkArea.C:596: error: call of overloaded 'QKeyEvent(QEvent::Type, int&, int, const QString&)' is ambiguous /usr/local/qt4//include/QtGui/qe

Re: Compile failure: younes branch

> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes: Bennett> Yes: Bennett> ld: warning multiple definitions of symbol _locale_charset Bennett> ../intl/libintl.a(localcharset.o) definition of Bennett> _locale_charset in section (__TEXT,__text) Bennett> /usr/lib/libiconv.dylib(localcharset.

Re: Compile failure: younes branch

Bennett Helm wrote: On Jun 27, 2006, at 12:06 PM, Abdelrazak Younes wrote: Just call me Holmes, Abdel Holmes ;-) Or is that Sherlock Younes? :-) Do you see any side effect WRT screen update or scrollbar slider position as Lars does? I should have mentioned. The screen updates fine, but

Re: Compile failure: younes branch

On Jun 27, 2006, at 12:06 PM, Abdelrazak Younes wrote: Just call me Holmes, Abdel Holmes ;-) Or is that Sherlock Younes? Here are some performance numbers on Mac for scrolling through the User's Guide using : trunk (Qt-4.1.3): 2 min, 10 sec (with graphics preview on, first time through);

Re: Compile failure: younes branch

> Does that mean you want this? Thanks.Could you send your config.log too? JMarc

Re: Compile failure: younes branch

Bennett Helm wrote: On Jun 27, 2006, at 5:12 AM, Abdelrazak Younes wrote: Bennett Helm wrote: On Jun 26, 2006, at 12:44 PM, Abdelrazak Younes wrote: You compiled Qt4 yourself right? I think that Qt needs some libraries to link with, libstdc++ most probably. Please verify that the final link

Re: Compile failure: younes branch

On Jun 27, 2006, at 10:26 AM, Jean-Marc Lasgouttes wrote: We'll have to look at the link command and understand why libintl defines it when it is already supported by your libiconv. Does that mean you want this? -- /bin/sh ../libtool --tag=CXX --mode=link g++ -fno-exceptions -Os - framework

Re: Compile failure: younes branch

On Jun 27, 2006, at 5:12 AM, Abdelrazak Younes wrote: Bennett Helm wrote: On Jun 26, 2006, at 12:44 PM, Abdelrazak Younes wrote: You compiled Qt4 yourself right? I think that Qt needs some libraries to link with, libstdc++ most probably. Please verify that the final link is done with g++ an

Re: Compile failure: younes branch

> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes: Bennett> Yes: Bennett> ld: warning multiple definitions of symbol _locale_charset Bennett> ../intl/libintl.a(localcharset.o) definition of Bennett> _locale_charset in section (__TEXT,__text) Bennett> /usr/lib/libiconv.dylib(localcharset.

Re: Compile failure: younes branch

On Jun 27, 2006, at 5:37 AM, Jean-Marc Lasgouttes wrote: "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: Abdelrazak> This is not related to your linking errors but those two Abdelrazak> messages is maybe an indication of what fails WRT to Mac Abdelrazak> an locales: /usr/bin/ld

Re: Compile failure: younes branch

> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: Abdelrazak> Jean-Marc Lasgouttes wrote: >>> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: >> Abdelrazak> I tried to set LANG=pl_PL and then to open a document and Abdelrazak> I got a crash... >> There was a ba

Re: Compile failure: younes branch

Jean-Marc Lasgouttes wrote: "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: Abdelrazak> I tried to set LANG=pl_PL and then to open a document and Abdelrazak> I got a crash... There was a bad translation of counters in pl.po. I updated it with the version from the 1.4 branch (an

Re: Compile failure: younes branch

> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: Abdelrazak> I tried to set LANG=pl_PL and then to open a document and Abdelrazak> I got a crash... There was a bad translation of counters in pl.po. I updated it with the version from the 1.4 branch (and italian too). Please try

Re: Compile failure: younes branch

Jean-Marc Lasgouttes wrote: "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: Abdelrazak> The good news is that locales is perfectly supported now Abdelrazak> by my msvc build. Once I get Aspell support, I will update Abdelrazak> my experimental package. Do you have the right chara

Re: Compile failure: younes branch

> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: Abdelrazak> The good news is that locales is perfectly supported now Abdelrazak> by my msvc build. Once I get Aspell support, I will update Abdelrazak> my experimental package. Do you have the right characters when using the Poli

Re: Compile failure: younes branch

Jean-Marc Lasgouttes wrote: "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: Abdelrazak> This is not related to your linking errors but those two Abdelrazak> messages is maybe an indication of what fails WRT to Mac Abdelrazak> an locales: /usr/bin/ld: warning multiple definitions

  1   2   3   >