Bug#763755: blender: SIGILL on startup

Matteo F. Vescovi mfvescovi at gmail.com
Thu Oct 2 12:43:30 UTC 2014


Control: tag -1 + upstream

Hi!

On 2014-10-02 at 13:54 (CEST), Daniele Forsi wrote:
> Dear Maintainer,
> 
> could Blender be changed to check if it is running on a supported CPU
> and fail with a nicely informative error message?
 
At [1] you can see that the former patch that used to check about the
compatibility of the CPU with Blender has been dropped since upstream
developers declared that a better (and elegant) solution was found and
that patch wasn't useful anymore.

> On my PC blender is terminated on startup with:
> Program received signal SIGILL, Illegal instruction.

Well, probably the upstream approach hasn't been efficient enough to
prevent all the cases. I already got in touch with them and we'll see
how to solve this long-persecuting issue.

Cheers.


[1] http://anonscm.debian.org/cgit/pkg-multimedia/blender.git/commit/?id=fce9104b648ad2d81fc82362eb9f377c6eb5641d

-- 
Matteo F. Vescovi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 956 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20141002/8943edf7/attachment.sig>


More information about the pkg-multimedia-maintainers mailing list