Hey,
this got fixed in the 5.6 branch and did not get forward merged yet.
https://codereview.qt-project.org/#/c/153305/
Please use that patch and the c++11 error should go away.
Thank you
Andy
Am 29.03.2016 um 03:57 schrieb Thiago Macieira:
> On segunda-feira, 28 de março de 2016 21:33:11 PDT P
On segunda-feira, 28 de março de 2016 21:33:11 PDT Partha Bagchi wrote:
> EXTRA_CXXFLAGS = -std=c++11 -DUNICODE -ffunction-sections
It's there, but it's not in your command-line, which had:
g++ -c -o project.o -DUNICODE -g -IZ:/src/qt5/qtbase/qmake
It's missing two options. I don't know how or
On Mon, Mar 28, 2016 at 9:25 PM, Thiago Macieira
wrote:
> On segunda-feira, 28 de março de 2016 18:30:22 PDT Partha Bagchi wrote:
> > > Looks like it's not compiling as C++11.
> >
> > Adding c++11 does not make any difference.
>
> configure should have got the flag from the mkspec. Can you check
On segunda-feira, 28 de março de 2016 18:30:22 PDT Partha Bagchi wrote:
> > Looks like it's not compiling as C++11.
>
> Adding c++11 does not make any difference.
configure should have got the flag from the mkspec. Can you check if qmake/
Makefile has a line with QMAKE_CXXFLAGS_CXX11? It probably
On Mon, Mar 28, 2016 at 6:49 PM, Partha Bagchi wrote:
>
>
> On Mon, Mar 28, 2016 at 4:44 PM, Thiago Macieira <
> thiago.macie...@intel.com> wrote:
>
>> On segunda-feira, 28 de março de 2016 17:13:56 PDT Rafael Roquetto wrote:
>> > Hey,
>> >
>> > 1. don't use msys shell.
>> > 2. make sure stuff li
On Mon, Mar 28, 2016 at 4:44 PM, Thiago Macieira
wrote:
> On segunda-feira, 28 de março de 2016 17:13:56 PDT Rafael Roquetto wrote:
> > Hey,
> >
> > 1. don't use msys shell.
> > 2. make sure stuff like sh.exe is not on your path
>
> Doesn't match my recommendation. I do use the msys shell and I d
On Mon, Mar 28, 2016 at 4:37 PM, Thiago Macieira
wrote:
> On segunda-feira, 28 de março de 2016 15:00:04 PDT Partha Bagchi wrote:
> > On Mon, Mar 28, 2016 at 1:09 PM, Thiago Macieira <
> thiago.macie...@intel.com>
> > wrote:
> > > On segunda-feira, 28 de março de 2016 12:34:38 PDT Partha Bagchi w
On segunda-feira, 28 de março de 2016 17:13:56 PDT Rafael Roquetto wrote:
> Hey,
>
> 1. don't use msys shell.
> 2. make sure stuff like sh.exe is not on your path
Doesn't match my recommendation. I do use the msys shell and I do have sh.exe
on PATH.
> 3. use configure.bat (not the configure she
On segunda-feira, 28 de março de 2016 15:00:04 PDT Partha Bagchi wrote:
> On Mon, Mar 28, 2016 at 1:09 PM, Thiago Macieira
> wrote:
> > On segunda-feira, 28 de março de 2016 12:34:38 PDT Partha Bagchi wrote:
> > > However, during configuration, I get errors like
> > > C:optsopt64-kdeincludeglibcon
Hey,
1. don't use msys shell.
2. make sure stuff like sh.exe is not on your path
3. use configure.bat (not the configure shell script)
4. use backslashes for -I and -L when passing arguments to configure
configure (...) -I C:\ICU\include -L C:\ICU\lib
5. for everything else, use forward-slas
On Mon, Mar 28, 2016 at 1:09 PM, Thiago Macieira
wrote:
> On segunda-feira, 28 de março de 2016 12:34:38 PDT Partha Bagchi wrote:
> > However, during configuration, I get errors like
> > C:optsopt64-kdeincludeglibconfig.h unknown command.
>
> Show the entire command that failed.
>
> 5.7 does not
On segunda-feira, 28 de março de 2016 12:34:38 PDT Partha Bagchi wrote:
> However, during configuration, I get errors like
> C:optsopt64-kdeincludeglibconfig.h unknown command.
Show the entire command that failed.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel O
On Mon, Mar 28, 2016 at 11:41 AM, Thiago Macieira wrote:
> On segunda-feira, 28 de março de 2016 09:28:14 PDT Partha Bagchi wrote:
> > I am building using a Windows command-line since ./configure chokes on
> > directory separators. For example, I cannot get glib support if I use the
> > Msys shel
On segunda-feira, 28 de março de 2016 09:28:14 PDT Partha Bagchi wrote:
> I am building using a Windows command-line since ./configure chokes on
> directory separators. For example, I cannot get glib support if I use the
> Msys shell.
Use forward slashes.
--
Thiago Macieira - thiago.macieira (AT
Hi,
My first post here.
I am trying to compile QT 5.7 with my toolchain. I must be doing something
silly and wrong: I get the following error:
jit\qv4regalloc.cpp:648:8: error: missing binary operator before token "("
#if CPU(X86) || CPU(X86_64)
^
Makefile.Release:16312: recipe for tar
Hi Giuseppe,
Unfortunatelly the patch still has not been reviewed. So without further
steps it will not be propagated anywhere. May you advise how to pass this
step? Maybe some other reviewer with more free time could take a look on
it? Who it can be?
Best regards,
Vyacheslav.
26 Мар 2016 г.
16 matches
Mail list logo