Re: [Development] 32bit linux build of qt5.10.0 w/ webengine

2018-01-04 Thread Thiago Macieira
On Thursday, 4 January 2018 23:40:40 -02 Christian Gagneraud wrote: > It's not just about what hardware you target, in my case, i cannot > build the codebase in 64 bits, simply because the code is not 64-bits > ready (mainly due to legacy old/complicated components): Not only the > code base is ful

Re: [Development] 32bit linux build of qt5.10.0 w/ webengine

2018-01-04 Thread Christian Gagneraud
On 5 January 2018 at 12:22, Thiago Macieira wrote: > On Thursday, 4 January 2018 20:52:40 -02 Christian Gagneraud wrote: >> On 5 January 2018 at 03:16, Kevin Kofler wrote: >> > Thiago Macieira wrote: >> >> In particular: -no-sse2. >> >> >> >> If you use that option, that means you're optimising f

Re: [Development] 32bit linux build of qt5.10.0 w/ webengine

2018-01-04 Thread Thiago Macieira
On Thursday, 4 January 2018 20:52:40 -02 Christian Gagneraud wrote: > On 5 January 2018 at 03:16, Kevin Kofler wrote: > > Thiago Macieira wrote: > >> In particular: -no-sse2. > >> > >> If you use that option, that means you're optimising for Pentium III and > >> earlier, not Pentium 4. All Pentiu

Re: [Development] 32bit linux build of qt5.10.0 w/ webengine

2018-01-04 Thread Christian Gagneraud
On 5 January 2018 at 03:16, Kevin Kofler wrote: > Thiago Macieira wrote: >> In particular: -no-sse2. >> >> If you use that option, that means you're optimising for Pentium III and >> earlier, not Pentium 4. All Pentium 4 processors have SSE2. I was looking at LEDE (a fork/merge of OpenWRT) recent

Re: [Development] 32bit linux build of qt5.10.0 w/ webengine

2018-01-04 Thread Thiago Macieira
On Thursday, 4 January 2018 12:16:37 -02 Kevin Kofler wrote: > Thiago Macieira wrote: > > In particular: -no-sse2. > > > > If you use that option, that means you're optimising for Pentium III and > > earlier, not Pentium 4. All Pentium 4 processors have SSE2. > > > > More importantly, SSE2 is *MA

Re: [Development] About the presence of /System/Library/Frameworks/Carbon.framework

2018-01-04 Thread Konstantin Tokarev
04.01.2018, 17:51, "Edward Welbourne" : > René J.V. Bertin:  Here's a silly one: configuring Qt for building on my Linux rig I was told  that I needed Xcode, and how to get it. :)  Long story short, it turns out that the configure script determines  whether it's building

Re: [Development] About the presence of /System/Library/Frameworks/Carbon.framework

2018-01-04 Thread Edward Welbourne
René J.V. Bertin: >>> Here's a silly one: configuring Qt for building on my Linux rig I was told >>> that I needed Xcode, and how to get it. :) >>> >>> Long story short, it turns out that the configure script determines >>> whether it's building on Mac by checking if the Carbon framework exists >>>

Re: [Development] 32bit linux build of qt5.10.0 w/ webengine

2018-01-04 Thread Kevin Kofler
Thiago Macieira wrote: > In particular: -no-sse2. > > If you use that option, that means you're optimising for Pentium III and > earlier, not Pentium 4. All Pentium 4 processors have SSE2. > > More importantly, SSE2 is *MANDATORY* for 64-bit builds. You may not turn > it off. The errors you are g

Re: [Development] Project ERROR: Could not find feature future.

2018-01-04 Thread Oswald Buddenhagen
On Thu, Jan 04, 2018 at 01:40:43PM +0300, Igor Mironchik wrote: > Yes, I did it, it helped. But I have one question: is it possible to > switch branch "automatically" for qt5? > yes, it is, as pointed out on https://wiki.qt.io/Building_Qt_5_from_Git init-repository --branch

Re: [Development] Project ERROR: Could not find feature future.

2018-01-04 Thread André Hartmann
Hi, Am 04.01.2018 um 12:12 schrieb Thiago Macieira: On Thursday, 4 January 2018 08:40:43 -02 Igor Mironchik wrote: Hi, On 04.01.2018 13:00, Thiago Macieira wrote: On Thursday, 4 January 2018 06:35:33 -02 Oswald Buddenhagen wrote: On Thu, Jan 04, 2018 at 09:27:06AM +0300, Igor Mironchik wrote:

Re: [Development] Project ERROR: Could not find feature future.

2018-01-04 Thread Igor Mironchik
Yes, I did it, it helped. But I have one question: is it possible to switch branch "automatically" for qt5? I know about git submodule foreach --recursive but it will now help. Not all submodules have dev, 5.10 branches... This is the solution, with ignoring the errors in the modules that don'

Re: [Development] Project ERROR: Could not find feature future.

2018-01-04 Thread Thiago Macieira
On Thursday, 4 January 2018 08:40:43 -02 Igor Mironchik wrote: > Hi, > > On 04.01.2018 13:00, Thiago Macieira wrote: > > On Thursday, 4 January 2018 06:35:33 -02 Oswald Buddenhagen wrote: > >> On Thu, Jan 04, 2018 at 09:27:06AM +0300, Igor Mironchik wrote: > >>> Maybe I need to checkout all projec

Re: [Development] Project ERROR: Could not find feature future.

2018-01-04 Thread Igor Mironchik
Hi, On 04.01.2018 13:00, Thiago Macieira wrote: On Thursday, 4 January 2018 06:35:33 -02 Oswald Buddenhagen wrote: On Thu, Jan 04, 2018 at 09:27:06AM +0300, Igor Mironchik wrote: Maybe I need to checkout all projects to dev branch? yes, you do. All projects in the same branch. Yes, I did

Re: [Development] Project ERROR: Could not find feature future.

2018-01-04 Thread Thiago Macieira
On Thursday, 4 January 2018 06:35:33 -02 Oswald Buddenhagen wrote: > On Thu, Jan 04, 2018 at 09:27:06AM +0300, Igor Mironchik wrote: > > Maybe I need to checkout all projects to dev branch? > > yes, you do. All projects in the same branch. -- Thiago Macieira - thiago.macieira (AT) intel.com S

Re: [Development] Project ERROR: Could not find feature future.

2018-01-04 Thread Oswald Buddenhagen
On Thu, Jan 04, 2018 at 09:27:06AM +0300, Igor Mironchik wrote: > Maybe I need to checkout all projects to dev branch? > yes, you do. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

[Development] CI down for a moment

2018-01-04 Thread Tony Sarajärvi
Hi all! We had situation where it seems like cachefilesd bugged and didn't do cache culling. Our hosts filled up and caches got messed up. After cleaning the corrupted images, we still had hosts having incorrect data in caches. So as a quick fix I'm redeploying all hosts now. It takes some time