[linux-audio-dev] regarding mobos and CPUs

[Fernando Pablo Lopez-Lezcano]

On Thu, 2004-05-06 at 07:53, Taybin Rutkin wrote:
> Yes, that was just an autotools problem.  It could have happened to a P4 if jack 
> was built on an AMD box.  It was more of a cross-compilation issue.

Yes, there is no problem with the AMD processors that I know of. This
was a packaging problem triggered by the autotools problem. In essence
the package itself was saying "I can run on any i386 cpu" so that
apt/rpm was happily installing it on a Duron processor (which is
compatible with the i386 instruction set). _But_ the contents of the
package did not agree with the label and I did not catch that before
releasing it :-) The executable itself had instructions that could _not_
execute in the Duron processor (but, for example, they would have worked
fine on more recent AMD processors). So the program segfaulted on
startup with an "illegal instruction" fault. Anyway, just to clarify
things...

-- Fernando

> -----Original Message-----
> From: Dave Phillips <dlphilp at bright.net>
> Sent: May 6, 2004 11:20 AM
> To: 
> 	The Linux Audio Developers' Mailing List <linux-audio-dev at music.columbia.edu>, 
> 	LAU Mail <linux-audio-user at music.columbia.edu>
> Subject: Re: [linux-audio-dev] regarding mobos and CPUs
> 
> Taybin Rutkin wrote:
> 
> >What is the problem with JACK and AMD cpus?  I haven't heard of one.
> >
> >  
> >
> Not so long ago a release of qjackctl in Planet C failed due to (IIRC) 
> JACK getting compiled with an SSE call (or calls) that killed it 
> completely on my Duron. The problem was simply and quickly solved, and 
> I'm perhaps off-base accusing JACK but that's where the problem came 
> from. Maybe it was a bad make ?
> 
> Anyway, if it's the opinion of the LAD developers that AMD is OK then 
> that's what I need to know. As I stated, I've had only that one 
> difficulty with AMD and Linux audio software, so I think I'm just being 
> paranoid.
> 
> Best,
> 
> dp
>