On Saturday 21 June 2014 18:29:43 Dmitry Shachnev wrote: > On Sat, Jun 21, 2014 at 6:15 PM, Lisandro Damián Nicanor Pérez Meyer > > <perezmeyer@gmail.com> wrote: > > I've tried to build it twice on an armhf porterbox and Dmitry Schanev > > tried on an armel qemu VM. In my case the porterbox would simply hang > > before reaching where the buildd gets, and I think the VM build also > > failed earlier. > FWIW my armhf build segfaulted, but armel build succeeded: > > http://95.85.27.130/builds/qtcreator_3.1.1+dfsg-1_armhf.build > http://95.85.27.130/builds/qtcreator_3.1.1+dfsg-1_armel.build Recently qtcreator failed much like this on mips. It turned out to be a memory issue and rebuilding on a buildd with more ram+swap did the trick. The build logs for qtcreator on arm* do not always fail in the same way and/or in the same point, plus Dmitry managed to get it to build without issues with an armel VM. So maybe it's also a memory issue. Which armel and armhf buildds have the most amount of ram+swap? I would like to see if the source tried to build there and else give it a try. Thanks in advance, Lisandro. -- Los errores ortográficos y de redacción fueron insertados con la única intención de testear sus conocimientos de la lengua castellana. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Attachment:
signature.asc
Description: This is a digitally signed message part.