On Fri, 2013-02-01 at 18:56 +0100, Sébastien Villemot wrote: > Sorry I forgot to Cc you in my previous email. Please see the email > attached. For the reply, please use [email protected] > > email message attachment, "Message transféré - Re: [Pkg-octave-devel] > Bug#699300: Bug#699300: #699300: reproducible here" > > -------- Forwarded Message -------- > > From: Sébastien Villemot <[email protected]> > > To: [email protected] > > Subject: Re: [Pkg-octave-devel] Bug#699300: Bug#699300: #699300: > > reproducible here > > Date: Fri, 01 Feb 2013 18:42:45 +0100 > > > > Le vendredi 01 février 2013 à 10:46 -0500, Jordi Gutiérrez Hermoso a > > écrit : > > > On 1 February 2013 10:40, Roland Mas <[email protected]> wrote: > > > > As suggested on IRC, I tried to reproduce this bug on my > > > > not-getting-any-younger laptop, and I did manage (using octave from > > > > backports, since it's squeeze). I include CPU info, since this seems to > > > > be relevant. > > > > > > Thanks for testing. The issue is probably that one or both of the > > > libblas3gf or libatlas3gf-base packages are compiled with features > > > SSE2 features or higher that some CPUs don't support. I now suspect > > > this is a duplicate of #690671 > > > > This is indeed very likely. > > > > Bill, you have two options: > > > > - uninstall libatlas3gf-base > > > > - alternatively, compile and install a custom ATLAS package as explained > > in /usr/share/doc/libatlas3gf-base/README.Debian.gz > > > > Please confirm that either solution fixes the bug. > > Sebastien, Thanks for tracking this down. My processor only supports SSE instructions, not SSE2. Uninstalling libatlas3gf-base solved my problem but I'll have to study the suggested debian documentation to better understand what was going on here.
Bill -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
