Bug#654428: blender: FTBFS: uses i386/amd64 specific register definitions on all architectures

2012-01-26 Thread Matteo F. Vescovi
Hi! On 25/01/2012 21:05, Kevin Roy wrote: As far as I and others have tested the patch, builds are now ok on ARM and KFreeBSD. I'm not sure on others but debian buildd servers will tell us :) . It builds fine even on ia64... it has been tested last night. But actually it doesn't build on

Bug#654428: blender: FTBFS: uses i386/amd64 specific register definitions on all architectures

2012-01-26 Thread Sergey Sharybin
Hi again, Commited patch to support more platforms to our trunk (http://projects.blender.org/scm/viewvc.php?view=revroot=bf-blenderrevision=43716) Hope it'll help make more users and platform maintainers happier, thanks to Kevin for it. I don't have sparc platform at all, so seeing error log

Bug#654428: blender: FTBFS: uses i386/amd64 specific register definitions on all architectures

2012-01-26 Thread Matteo F. Vescovi
Hi! On 26/01/2012 11:40, Sergey Sharybin wrote: Hi again, Commited patch to support more platforms to our trunk (http://projects.blender.org/scm/viewvc.php?view=revroot=bf-blenderrevision=43716) Hope it'll help make more users and platform maintainers happier, thanks to Kevin for it. OK,

Bug#654428: blender: FTBFS: uses i386/amd64 specific register definitions on all architectures

2012-01-26 Thread Sergey Sharybin
Ok, looked through logs. Commited fix (rev43718 in our svn trunk) which should make some platforms work nicer (at least fix currently reported compilation errors). This should help on spark, s390x, s390, mips platforms. Still can see some issues related on REG_EIP and mcontext_t things. Not sure

Bug#654428: blender: FTBFS: uses i386/amd64 specific register definitions on all architectures

2012-01-26 Thread Matteo F. Vescovi
Hi! On 26/01/2012 12:23, Sergey Sharybin wrote: Ok, looked through logs. Commited fix (rev43718 in our svn trunk) which should make some platforms work nicer (at least fix currently reported compilation errors). This should help on spark, s390x, s390, mips platforms. Good to know. Still can

Bug#654428: blender: FTBFS: uses i386/amd64 specific register definitions on all architectures

2012-01-25 Thread Sergey Sharybin
Hi, We've got quite the same error with FreeBSD support. Attached patch should fix this issue. If it will still fail, would be helpful to have config.h generated by configure script of glog itself (which can be found here http://code.google.com/p/google-glog/). But if proposed patch will work

Bug#654428: blender: FTBFS: uses i386/amd64 specific register definitions on all architectures

2012-01-25 Thread Kevin Roy
Hi Sergey, Le 25/01/2012 16:04, Sergey Sharybin a écrit : Hi, We've got quite the same error with FreeBSD support. Attached patch should fix this issue. If it will still fail, would be helpful to have config.h generated by configure script of glog itself (which can be found here

Bug#654428: blender: FTBFS: uses i386/amd64 specific register definitions on all architectures

2012-01-25 Thread Sergey Sharybin
Hi, Good patch, don't think mine is needed to be added (the same changes are already made). Don't have access to non-i386/amd64 machines, but 0011-fix_FTBFS_with_libmv.patch looks fine and if it's indeed resolves build issues i would be happy to commit it to blender's trunk. On Wed, Jan 25, 2012

Bug#654428: blender: FTBFS: uses i386/amd64 specific register definitions on all architectures

2012-01-25 Thread Kevin Roy
Le 25/01/2012 20:50, Sergey Sharybin a écrit : Hi, Good patch, don't think mine is needed to be added (the same changes are already made). Don't have access to non-i386/amd64 machines, but 0011-fix_FTBFS_with_libmv.patch looks fine and if it's indeed resolves build issues i would be happy

Bug#654428: blender: FTBFS: uses i386/amd64 specific register definitions on all architectures

2012-01-04 Thread peter green
retitle 654428 blender: FTBFS: uses i386/amd64 specific register definitions on all architectures thanks Christoph Egger wrote: Your package failed to build on the buildds: More accurately it built successfullyy on the i386 buildd but failed on all the other buildds that tried to build it