Brendan Jones wrote:
> On 15/02/16 07:46, Orcan Ogetbil wrote:
>> The new version of qjackctl, which now depends on qt5. We cannot do
>> the update without fixing this. As far as I can tell, the qjackctl
>> does not use the QMAKE_DEFAULT_INCDIRS directly. The offending flags
>> come through qmake.
On 15/02/16 07:46, Orcan Ogetbil wrote:
The new version of qjackctl, which now depends on qt5. We cannot do
the update without fixing this. As far as I can tell, the qjackctl
does not use the QMAKE_DEFAULT_INCDIRS directly. The offending flags
come through qmake.
Other than this the new qsynth a
Orcan Ogetbil wrote:
> On 16 February 2016 at 13:08, Rex Dieter wrote:
>> So, 2 options (not mutually exclusive):
>>
>> * fix configure to not add /usr/include to ac_incpath
>> * fix src/src.pri.in to comment-out (or remove) the line starting with
>> INCLUDEPATH += (I don't think it's needed)
>>
>
On 16 February 2016 at 13:08, Rex Dieter wrote:
> So, 2 options (not mutually exclusive):
>
> * fix configure to not add /usr/include to ac_incpath
> * fix src/src.pri.in to comment-out (or remove) the line starting with
> INCLUDEPATH += (I don't think it's needed)
>
Yes, I could use those to work
Rex Dieter wrote:
> Orcan Ogetbil wrote:
>
>> On 14 February 2016 at 18:42, Rex Dieter wrote:
>
>>> what package is affected here?
>>>
>>> I have a suspicion that QMAKE_DEFAULT_INCDIRS is being misused in this
>>> context.
>>
>> The new version of qjackctl, which now depends on qt5. We cannot d
Orcan Ogetbil wrote:
> On 15 February 2016 at 01:46, Orcan Ogetbil wrote:
>>
>> The new version of qjackctl, which now depends on qt5. We cannot do
>> the update without fixing this. As far as I can tell, the qjackctl
>> does not use the QMAKE_DEFAULT_INCDIRS directly. The offending flags
>> come
Orcan Ogetbil wrote:
> On 14 February 2016 at 18:42, Rex Dieter wrote:
>> what package is affected here?
>>
>> I have a suspicion that QMAKE_DEFAULT_INCDIRS is being misused in this
>> context.
>
> The new version of qjackctl, which now depends on qt5. We cannot do
> the update without fixing th
On 15/02/16 22:24 -0500, Orcan Ogetbil wrote:
On 2 February 2016 at 07:54, Jakub Jelinek wrote:
That said, why does it bother to do such a mess? Does it think the g++
driver is not able to do that itself?
I am not sure why qmake-qt5 doesn't want to trust gcc for the system
include dirs, but
On 2 February 2016 at 07:54, Jakub Jelinek wrote:
>
> That said, why does it bother to do such a mess? Does it think the g++
> driver is not able to do that itself?
>
I am not sure why qmake-qt5 doesn't want to trust gcc for the system
include dirs, but well.. it doesn't.
I reduced the problem do
On 15 February 2016 at 01:46, Orcan Ogetbil wrote:
>
> The new version of qjackctl, which now depends on qt5. We cannot do
> the update without fixing this. As far as I can tell, the qjackctl
> does not use the QMAKE_DEFAULT_INCDIRS directly. The offending flags
> come through qmake.
>
Here is a s
On 14 February 2016 at 18:42, Rex Dieter wrote:
> Orcan Ogetbil wrote:
>
>> The current (as of this email) qt5-qtbase is built with GCC6, but the
>> issue persists.
>> The builds seem fine with the above QMAKE_DEFAULT_INCDIRS line removed
>> manually. Should this issue be fixed in the qt5-qtbase pa
Orcan Ogetbil wrote:
> The current (as of this email) qt5-qtbase is built with GCC6, but the
> issue persists.
> The builds seem fine with the above QMAKE_DEFAULT_INCDIRS line removed
> manually. Should this issue be fixed in the qt5-qtbase package?
what package is affected here?
I have a suspi
On 2 February 2016 at 07:50, Sandro Mani wrote:
> On 02.02.2016 13:38, Jakub Jelinek wrote:
>> On Tue, Feb 02, 2016 at 01:32:17PM +0100, Sandro Mani wrote:
>> Don't use -isystem /usr/include for C++, unless you also include first all
>> the C++ include directories as -isystem too. Why do you need
On Tue, Feb 02, 2016 at 01:50:58PM +0100, Sandro Mani wrote:
>
>
> On 02.02.2016 13:38, Jakub Jelinek wrote:
> >On Tue, Feb 02, 2016 at 01:32:17PM +0100, Sandro Mani wrote:
> >>Hi
> >>
> >>qt-creator builds have started to fail, I've reduced the failure down to
> >>having "-isystem /usr/include"
On 02.02.2016 13:38, Jakub Jelinek wrote:
On Tue, Feb 02, 2016 at 01:32:17PM +0100, Sandro Mani wrote:
Hi
qt-creator builds have started to fail, I've reduced the failure down to
having "-isystem /usr/include" in the command line:
Don't use -isystem /usr/include for C++, unless you also incl
On Tue, Feb 02, 2016 at 01:32:17PM +0100, Sandro Mani wrote:
> Hi
>
> qt-creator builds have started to fail, I've reduced the failure down to
> having "-isystem /usr/include" in the command line:
Don't use -isystem /usr/include for C++, unless you also include first all
the C++ include directori
Hi
qt-creator builds have started to fail, I've reduced the failure down to
having "-isystem /usr/include" in the command line:
$ cat test.cpp
#include
$ g++ -isystem /usr/include -c -o test.o test.cpp
In file included from /usr/include/c++/6.0.0/bits/stl_algo.h:59:0,
from /
17 matches
Mail list logo
