On quinta-feira, 17 de março de 2016 17:14:45 PDT Samuel Gaist wrote:
> > /usr/bin/clang++ -c -O3 -march=native -g -ffunction-sections -O2 -g -fPIC
> > -std=c++11
[...]
> > -I/Users/bertin/work/src/new/Qt/qt-everywhere-opensource-src-5.6.0/qtbase
> > /mkspecs/macx-clang
> Hi,
>
> Looks like
Thiago Macieira wrote:
> Ok, I'll send the change to remove it. People will not be happy.
No, indeed, even I won't be now that I found a workaround that's easier than
editing qmake.conf .
> That is an answer by itself. The fact that only the src/tools Makefiles are
> affected is a red
On quinta-feira, 17 de março de 2016 11:38:58 PDT Thiago Macieira wrote:
> > - -stdlib=libc++ appear to be missing only from CXXFLAGS in the Makefiles
> > under qtbase/src/tools
>
> Hmm... those are "bootstrapped" tools. But I can't find anything that
> overrides QMAKE_CXXFLAGS.
Can you confirm
On sexta-feira, 18 de março de 2016 11:27:38 PDT René J. V. Bertin wrote:
> > Autoconf-based configure scripts override the default settings.
>
> Another thing I'll take your word on, with the caveat outlined above. I've
> a whole collection of wrapper scripts that allow me to build
>
Thiago Macieira wrote:
> The proper way of adding options is to modify the mkspec's qmake.conf file
qmake.conf or .qmake.conf?
>> Checking my build scripts, I can confirm that CFLAGS and CXXFLAGS are set
>> *through the environment*, not by any direct action of mine.
>
> Yeah, not tested. This
On 17 mars 2016, at 16:36, René J.V. Bertin wrote:
> Hi,
>
> I'm running into an issue building Qt 5.6.0 on OS X 10.9.5 :
>
> gmake[3]: Entering directory
> '/.../qt5-kde-devel/work/build/qtbase/src/tools/bootstrap'
> /usr/bin/clang++ -c -O3 -march=native -g
Thiago Macieira wrote:
> The hint is in that "-O3 -march=native" in the command-line. The only place
> where "-march=native" shows up in the Qt sources is part of ANGLE [*], which
> is never compiled on OS X.
>
> So I conclude that René has overwritten QMAKE_CXXFLAGS.
Couple observations:
- I
Thiago Macieira wrote:
>> No, that's not true. AFAICR there were plenty of other Makefiles that did
>> have the option.
>
> Which ones?
The ones that scrolled off my history ;)
Seriously, to answer that question I'd have to restart a build without my fix,
so
are you truly interested to
On quinta-feira, 17 de março de 2016 22:06:09 PDT René J. V. Bertin wrote:
> > That is an answer by itself. The fact that only the src/tools Makefiles
> > are
> > affected is a red herring: you only have those Makefiles to look into.
>
> No, that's not true. AFAICR there were plenty of other
On Thursday March 17 2016 17:14:45 Samuel Gaist wrote:
> Hi,
>
> Looks like it's not using
>
> QMAKE_CXXFLAGS+= -stdlib=libc++
> QMAKE_LFLAGS += -stdlib=libc++
>
> However, why, I don't know.
Good eye, that's it! At least the compile command cited completes OK with that
additional
On quinta-feira, 17 de março de 2016 18:38:40 PDT René J. V. Bertin wrote:
> Couple observations:
> - I am doing nothing different from what I'm doing while building Qt 5.5.1
> - -stdlib=libc++ appear to be missing only from CXXFLAGS in the Makefiles
> under qtbase/src/tools
Hmm... those are
On quinta-feira, 17 de março de 2016 20:48:19 PDT René J. V. Bertin wrote:
> Thiago Macieira wrote:
> > The proper way of adding options is to modify the mkspec's qmake.conf file
>
> qmake.conf or .qmake.conf?
mkspec/macx-clang/qmake.conf
> >> Checking my build scripts, I can confirm that
12 matches
Mail list logo