On 10/10/2014 09:47 AM, Matteo F. Vescovi wrote:
>
> Then, feel free to provide an updated patch. I'll give it a try.
Here. but it's against the .71, and looks pretty much the same as the
earlier one. I don't have enough free space to dare the pbuilder thing.
I also added that architecture.mk ment
Hi!
On Fri, Oct 10, 2014 at 9:15 AM, Johann Klammer wrote:
> On 10/10/2014 08:48 AM, Matteo F. Vescovi wrote:
> >
> > No, it doesn't. Your patch wasn't applied in 2.71.
> >
> I modified it locally...
>
Then, feel free to provide an updated patch. I'll give it a try.
> > Oh, gotta check this e
On 10/10/2014 08:48 AM, Matteo F. Vescovi wrote:
>
> No, it doesn't. Your patch wasn't applied in 2.71.
>
I modified it locally...
>
>
> Oh, gotta check this either... but I've no X on my laptop at the moment.
>
> Thanks for reporting.
>
Not sure it's a bug.. it's quite possible they don't s
On 10/09/2014 03:01 PM, Matteo F. Vescovi wrote:
> Hi again!
>
> On 2014-10-09 at 14:39 (CEST), Matteo F. Vescovi wrote:
>> Re-applying it with next upcoming revision. Sorry for the mess.
>
> FTR, test build on i386 with your patch applied on top of
> 2.72 now fails [1].
>
> I hope to find a sol
Hi again!
On 2014-10-09 at 14:39 (CEST), Matteo F. Vescovi wrote:
> Re-applying it with next upcoming revision. Sorry for the mess.
FTR, test build on i386 with your patch applied on top of
2.72 now fails [1].
I hope to find a solution soon.
Cheers.
[1]
http://debomatic-i386.debian.net/distr
Hi!
On 2014-10-09 at 02:12 (CEST), Johann Klammer wrote:
> Do you have a URL to that statement?
Actually, I don't have any :-(
> Because if they still build their x86 package inside an i386 emulator
> like before, that thing is not an actual bug upstream and will thus
> /never/ get fixed.
OK, t
On Thu, 2 Oct 2014 14:43:30 +0200 "Matteo F. Vescovi"
wrote:
> 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 err
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
Processing control commands:
> tag -1 + upstream
Bug #763755 [blender] blender: SIGILL on startup
Added tag(s) upstream.
--
763755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: blender
Version: 2.71+dfsg1-1
Severity: important
Dear Maintainer,
could Blender be changed to check if it is running on a supported CPU and fail
with a nicely informative error message?
On my PC blender is terminated on startup with:
Program received signal SIGILL, Illegal instruction
10 matches
Mail list logo
