On quinta-feira, 21 de dezembro de 2017 22:00:32 -02 tomek wrote:
> And it works also for me too, but command executed during 'configure'
> script execution lacks -std=c++11 flag:
Ah, so that is the problem.
It's passing -std=gnu++11 here, for me.
Can you attach the entire config.log? Make sure
2017-12-21 13:03 GMT+01:00 Thiago Macieira :
> On quinta-feira, 21 de dezembro de 2017 02:11:52 CST tomek wrote:
> > I should think about airports and hotels... sorry for that.
> >
> > But getting back to the topic, I've started build configuration as
> usually
> >
On quinta-feira, 21 de dezembro de 2017 02:11:52 CST tomek wrote:
> I should think about airports and hotels... sorry for that.
>
> But getting back to the topic, I've started build configuration as usually
> using GCC - without passing this flag at all. But it failed with this error:
>
> ERROR:
On Wednesday December 20 2017 18:43:51 Allan Sandfeld Jensen wrote:
Another interesting one in this context: -gtoggle . I'm going to try that one
with QWE which so far has proven to be very resilient to preventing debug info
from being generated (it QtBase was built with -g?). That should
On Mittwoch, 20. Dezember 2017 18:32:16 CET Konstantin Tokarev wrote:
> 20.12.2017, 20:17, "René J. V. Bertin" :
> > Thiago Macieira wrote:
> >> A Qt release build builds with -g1 instead of -g, which should be
> >> sufficient for backtraces but not for debugging.
> >
> >
I should think about airports and hotels... sorry for that.
But getting back to the topic, I've started build configuration as usually
using GCC - without passing this flag at all. But it failed with this error:
ERROR: C++11 is required and is missing or failed to compile.
So I've started
On quarta-feira, 20 de dezembro de 2017 19:28:46 CST Thiago Macieira wrote:
> > https://forum.qt.io/topic/86052/qt-5-10-0-compile-with-clang-on-ubuntu-17->
> > > 10
> >
> > Hope you are tolerating links to qt's forum here.
>
> Links are fine. But in the interest of expediency, you should post
On quarta-feira, 20 de dezembro de 2017 15:53:53 CST tomek wrote:
> Since you have started such a discussion I want to ask you if you have
> tried to compile latest Qt releases with clang on linux?
I have. It compiles just fine.
I haven't *run* anything with it for ages, though.
> I'm having
On Wednesday December 20 2017 22:53:53 tomek wrote:
> Since you have started such a discussion I want to ask you if you have
> tried to compile latest Qt releases with clang on linux?
No, I haven't myself. Sometimes I do follow the advice I get when I ask for it
and in this case I didn't have
Since you have started such a discussion I want to ask you if you have
tried to compile latest Qt releases with clang on linux?
I'm having some problems with I've described in more details on qt's forum:
https://forum.qt.io/topic/86052/qt-5-10-0-compile-with-clang-on-ubuntu-17-10
Hope you are
20.12.2017, 20:17, "René J. V. Bertin" :
> Thiago Macieira wrote:
>
>> A Qt release build builds with -g1 instead of -g, which should be sufficient
>> for backtraces but not for debugging.
>
> That's interesting, the option doesn't show up in g++ --verbose --help so I
>
Thiago Macieira wrote:
> A Qt release build builds with -g1 instead of -g, which should be sufficient
> for backtraces but not for debugging.
That's interesting, the option doesn't show up in g++ --verbose --help so I
wasn't aware it existed. There's also -gz I see now, which could be useful
On quarta-feira, 20 de dezembro de 2017 08:32:49 PST René J. V. Bertin wrote:
> Talking about keeping the binaries compact: is there a way to build or strip
> specific components from most debug information, let's say except that
> which is needed to get backtraces with line numbers (and function
20.12.2017, 19:33, "René J. V. Bertin" :
> Talking about keeping the binaries compact: is there a way to build or strip
> specific components from most debug information, let's say except that which
> is
> needed to get backtraces with line numbers (and function names)?
Talking about keeping the binaries compact: is there a way to build or strip
specific components from most debug information, let's say except that which is
needed to get backtraces with line numbers (and function names)?
R.
___
Interest mailing list
On Monday, 18 December 2017 12:13:42 PST Allan Sandfeld Jensen wrote:
> It is not really much slower anymore
> though. It used to be slower because the final compilation was all in a
> single process and single threaded, but that part is now multithreaded.
>From experience, it's *not* slower.
On Montag, 18. Dezember 2017 20:55:42 CET René J. V. Bertin wrote:
> Thiago Macieira wrote:
> > It doesn't, because the debug information is not loaded in the first
> > place.
> > When using readelf, note how the "A" flag is missing for those sections.
>
> So it has to skip certain, possibly
On Monday, 18 December 2017 11:55:42 PST René J. V. Bertin wrote:
> Thiago Macieira wrote:
> > It doesn't, because the debug information is not loaded in the first
> > place.
> > When using readelf, note how the "A" flag is missing for those sections.
>
> So it has to skip certain, possibly
Thiago Macieira wrote:
> It doesn't, because the debug information is not loaded in the first place.
> When using readelf, note how the "A" flag is missing for those sections.
So it has to skip certain, possibly considerable parts of the file while
loading
it, rather than simply doing some
On Monday, 18 December 2017 06:38:20 PST René J.V. Bertin wrote:
> Hi,
>
> Not to start a flame war, but are there clear differences between building
> Qt (on Linux) with clang (5.0) vs. GCC (7.2) that make the one or the other
> a better choice for certain domains of application?
>
> Link-time
Allan Sandfeld Jensen wrote:
Hi,
> It is pretty much the same. I would recommend gcc because that is default on
> Linux and the most likely to compile warning free and support most
> configurations.
That's more or less what I expected. The only mostly systematic difference I
see
(on all
On Montag, 18. Dezember 2017 15:38:20 CET René J.V. Bertin wrote:
> Hi,
>
> Not to start a flame war, but are there clear differences between building
> Qt (on Linux) with clang (5.0) vs. GCC (7.2) that make the one or the other
> a better choice for certain domains of application?
>
> Link-time
Hi,
Not to start a flame war, but are there clear differences between building Qt
(on Linux) with clang (5.0) vs. GCC (7.2) that make the one or the other a
better choice for certain domains of application?
Link-time optimisation is out of the question (too costly on my hardware, which
is
23 matches
Mail list logo