Hi,
I've just heard from a friend about that amazing stuff, I'm so excited, you've
got to take a look <http://belief.ryansrally.org/lnfus>
Yours, Gunnar Wolf
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@li
Francesco Poli dijo [Wed, Oct 07, 2015 at 11:50:53PM +0200]:
> I personally think it is indeed relevant.
>
> Let me try to explain.
> The term "further restrictions" is meant "with respect to the
> GPL terms", not "with respect to GPL terms + any terms added by the
> copyright holder".
> Hence rel
Matteo F. Vescovi dijo [Fri, Mar 28, 2014 at 08:47:31AM +0100]:
> I didn't forget you... the simple answer is that I don't know how to fix
> this, if there's a fix ;-)
>
> Anyhow, given that it's a python-related issue (iirc), could you please
> test if v2.70 release (now in experimental) changes
Forgot to comment about this for too long — Blender does /not/ run
either on armel. But it also fails to die — I left it (apparently)
running for over a full day, and it didn't seem to make anything.
___
pkg-multimedia-maintainers mailing list
pkg-multim
One more data point: I installed an armel chroot in the same machine
where Blender is segfaulting on me, and it seems to work fine. That
means, Blender is currently running and trying to render an image... I
guess it will take quite a bit to succeed, having (the software) no
hardfloat support.
___
While I continue to learn the basics of gdb, this seems to confirm a
stack overflow: Several of the threads have corrupt stacks.
(gdb) thread apply all backtrace
Thread 6 (Thread 0x326fd240 (LWP 4977)):
#0 0x2b1adf94 in __libc_do_syscall () from
/lib/arm-linux-gnueabihf/libpthread.so.0
#1 0x2b1
found 739194 2.69-4
thanks
I did a clean Sid reinstall, and the bug is still present in the
current version.
Blender now attempts to generate a file to aid debugging, although it
crashed too early for this file ot be of use:
$ blender -noaudio -b
Color management: using fallback mode for
I'm providing some further data points, guided by the kind souls in
#debian-arm ;-)
After installing gdb, blender-dbg and python3.2-dbg, I ran blender
through gdb, and got the following output:
$ gdb --args blender -b -noaudio
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation
Subject: blender: Segfaults at startup on armhf
Package: blender
Version: 2.63a-1
Severity: important
I'm trying to test Blender's performance under an armhf machine;
sadly, whatever I do to try and start Blender up results in a
segfault.
Either starting Blender up with a file to process or start
Alessandro Ghedini dijo [Thu, Dec 05, 2013 at 07:16:50PM +0100]:
> > Ruby1.8 is scheduled to be removed before the Jessie release. You can
> > apply the trivial patch I am inlining here to make it work under newer
> > Ruby releases (including 1.9.1, which will be Jessie's default).
> >
> > This pa
Package: ecasound
Version: 2.9.0-1
Severity: important
Tags: patch
Hi,
Your package depends on the obsolete 1.8 version of Ruby.
Ruby1.8 is scheduled to be removed before the Jessie release. You can
apply the trivial patch I am inlining here to make it work under newer
Ruby releases (including 1
11 matches
Mail list logo
