On 08.05.2017 09:47, Thiago Macieira wrote:
On Sunday, 7 May 2017 22:56:53 PDT Sergio Martins wrote:
On 2017-05-06 16:00, Thiago Macieira wrote:
Someone could do that. I'd even appreciate just a backtrace from the
deadlocked application.
Have you asked the CI guys for such backtrace ? Why i
On Sunday, 7 May 2017 22:56:53 PDT Sergio Martins wrote:
> On 2017-05-06 16:00, Thiago Macieira wrote:
> > Someone could do that. I'd even appreciate just a backtrace from the
> > deadlocked application.
>
> Have you asked the CI guys for such backtrace ? Why isn't there a JIRA
> issue for this ?
Hi,
why can't we just keep these symbols around without exporting them through a
header file and make them simply forward to the global new/delete operators? If
we don't export them in a header at least newly compiled code would stop using
them, and old code would continue working like that.
C
On 2017-05-06 16:00, Thiago Macieira wrote:
Someone could do that. I'd even appreciate just a backtrace from the
deadlocked application.
Have you asked the CI guys for such backtrace ? Why isn't there a JIRA
issue for this ?
Regards,
--
Sérgio Martins | sergio.mart...@kdab.com | Senior Soft
On Sunday, 7 May 2017 12:43:39 PDT Konstantin Tokarev wrote:
> 07.05.2017, 22:43, "Thiago Macieira" :
> > On Sunday, 7 May 2017 12:26:02 PDT Konstantin Tokarev wrote:
> >> I'm doing embedded software development, and wouldn't even consider
> >> including emulated builds into my pipeline.
> >
> >
07.05.2017, 22:43, "Thiago Macieira" :
> On Sunday, 7 May 2017 12:26:02 PDT Konstantin Tokarev wrote:
>> I'm doing embedded software development, and wouldn't even consider
>> including emulated builds into my pipeline.
>
> Then if you have a need for QtDBus, you'll maybe step up and help us so
On Sunday, 7 May 2017 12:26:02 PDT Konstantin Tokarev wrote:
> I'm doing embedded software development, and wouldn't even consider
> including emulated builds into my pipeline.
Then if you have a need for QtDBus, you'll maybe step up and help us solve
this one-year-old issue.
--
Thiago Macieira
07.05.2017, 19:24, "Thiago Macieira" :
> On Sunday, 7 May 2017 03:20:26 PDT Ville Voutilainen wrote:
>> On 6 May 2017 at 22:48, Thiago Macieira wrote:
>> > Second, compiling to ARM requires cross-compilation. Since the problem
>> > happens because of cross-compilation, it happens for all ARM
On Sunday, 7 May 2017 03:20:26 PDT Ville Voutilainen wrote:
> On 6 May 2017 at 22:48, Thiago Macieira wrote:
> > Second, compiling to ARM requires cross-compilation. Since the problem
> > happens because of cross-compilation, it happens for all ARM builds.
>
> Perhaps we should get ARM hardware s
On 7 May 2017 at 18:36, René J. V. Bertin wrote:
> Ville Voutilainen wrote:
>
>> Perhaps we should get ARM hardware so that we can do ARM builds
>> without cross-compilation. :)
>
> Not a single Qt dev who'd be willing to donate his/her old phone or Raspberry
> for this purpose? ;)
I was actual
Ville Voutilainen wrote:
> Perhaps we should get ARM hardware so that we can do ARM builds
> without cross-compilation. :)
Not a single Qt dev who'd be willing to donate his/her old phone or Raspberry
for this purpose? ;)
___
Development mailing list
On 6 May 2017 at 22:48, Thiago Macieira wrote:
> Second, compiling to ARM requires cross-compilation. Since the problem happens
> because of cross-compilation, it happens for all ARM builds.
Perhaps we should get ARM hardware so that we can do ARM builds
without cross-compilation. :)
___
Thiago Macieira wrote:
> > First, because the CI stops at the moment the first problem happens. So we
> > don't know where else it may have happened. We only know where it did
happen.
Oh, right. I assumed that there were independent builders for the different
platforms.
> Ok, here you go: I've
13 matches
Mail list logo
