On Sunday 06 March 2016 03:07:57 Kevin Kofler wrote:
> Knoll Lars wrote:
> > Curtis Mitch wrote:
> >>Ferocious Triceratops Baring Fearsome Strength? Phew. I thought we'd
> >>gotten rid of all of those!
> >>
> > Took me two minutes to parse that one as well. Failure to build from
> > source.
>
> FT
Knoll Lars wrote:
> Curtis Mitch wrote:
>>Ferocious Triceratops Baring Fearsome Strength? Phew. I thought we'd
>>gotten rid of all of those!
>
> Took me two minutes to parse that one as well. Failure to build from
> source.
FTBFS is an acronym that, as far as I can tell, originated from Debian, b
2016-03-03 16:51 GMT+01:00 Thiago Macieira :
> On quinta-feira, 3 de março de 2016 10:51:40 PST Roland Winklmeier wrote:
> > No matter if I download the source from download.qt.io or clone from git
> > and run the normal build as configured in CI, I get the build error. I'm
> > not changing any fl
On quinta-feira, 3 de março de 2016 10:51:40 PST Roland Winklmeier wrote:
> No matter if I download the source from download.qt.io or clone from git
> and run the normal build as configured in CI, I get the build error. I'm
> not changing any flags. So my and CI configuration should be exactly the
> -Original Message-
> From: Development [mailto:development-
> bounces+kai.koehne=theqtcompany@qt-project.org] On Behalf Of
> Thiago Macieira
> Sent: Thursday, March 03, 2016 9:14 AM
> To: development@qt-project.org
> Subject: Re: [Development] How can Qt 5.6.0
[Development] How can Qt 5.6.0 MinGW pass in CI with
> QTBUG-49971 open?
>
> 2016-03-03 9:14 GMT+01:00 Thiago Macieira <mailto:thiago.macie...@intel.com> >:
>
>
> On quinta-feira, 3 de março de 2016 00:06:41 PST Thiago Macieira
> wrote:
> > On quint
2016-03-03 9:14 GMT+01:00 Thiago Macieira :
> On quinta-feira, 3 de março de 2016 00:06:41 PST Thiago Macieira wrote:
> > On quinta-feira, 3 de março de 2016 08:56:35 PST Roland Winklmeier wrote:
> > > So how is it possible that this error does not show up in CI? I did
> > > download the Qt MinGW
ay, 3 March 2016 9:07 AM
>> To: development@qt-project.org
>> Subject: Re: [Development] How can Qt 5.6.0 MinGW pass in CI with QTBUG-
>> 49971 open?
>>
>> On quinta-feira, 3 de março de 2016 08:56:35 PST Roland Winklmeier wrote:
>> > So how is it possible tha
> -Original Message-
> From: Development [mailto:development-
> bounces+mitch.curtis=theqtcompany@qt-project.org] On Behalf Of Thiago
> Macieira
> Sent: Thursday, 3 March 2016 9:07 AM
> To: development@qt-project.org
> Subject: Re: [Development] How can Qt 5.6.0
On quinta-feira, 3 de março de 2016 00:06:41 PST Thiago Macieira wrote:
> On quinta-feira, 3 de março de 2016 08:56:35 PST Roland Winklmeier wrote:
> > So how is it possible that this error does not show up in CI? I did
> > download the Qt MinGW 4.9 version, so CI should fail to build.
>
> -Wundef
On quinta-feira, 3 de março de 2016 08:56:35 PST Roland Winklmeier wrote:
> So how is it possible that this error does not show up in CI? I did
> download the Qt MinGW 4.9 version, so CI should fail to build.
-Wundef is not enabled by either -Wall or -Wextra. It's entirely correct C
source to #if
Dear list,
I'm trying to understand a strange situation and hope you can enlighten me.
In December I have raised QTBUG-49971 (a FTBFS bug) since it was not
possible to build MinGW 4.9 with the alpha sources and also from git since
then. The issue is obvious: Commit e19bedc8466a6b8086a0048b7b88c0f6
12 matches
Mail list logo
