[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: kdelibs in sid depends libjack0.80.0-0 which depends jackd; see 248665



> >>That was good to know.  But still when I try:
> >>
> >>jackd -d alsa

Is that enough?  I think the minimum is "jackd -d alsa -d hw:0" or something 
like that.  Maybe I'm wrong.  I usually run it with qjackctl anyway.

> >IMHO binary is optimised to use instructions that your cpu does not
> > support (MMX, SSE,  SSE2 , 3DNow!, CMOV).
>
> K6-II 350.  It does have mmx and 3dnow.  I guess sse is an Intel thing.
> Not sure about cmov yet.

I think everything is  *supposed* to be built for i386, isn't it?  But yes, I 
agree this is bound to be something with the arch target for the binary.  The 
K6 is rare enough that the problem could well have slipped under the radar 
all this time.

I guess, therefore, about all you can do is play with recompiling it from 
source, for the correct arch.  Or file a bug report and hope the package 
maintainer can help you sort it out.

Hrm.  This source is pretty messy, with a gob of patches and whanots.  I don't 
see any --with-arch-stuff= target, but I do see it compiles with -O3

In of itself, that's not unusual or particularly worrisome, but some of our 
Rosegarden users with an obscure version of gcc on some version of SuSE had 
bizarre problems due to compiler optimizations, and we had them compile with 
-O0 instead, which took care of it.  (That relates to this case because 
obscure problems as a result of -O3 on certain architectures is not 
unprecedented, even though I freely admit this is a big reach.)

You might give that a quick try and see if it helps.  Just

apt-get source libjack0.80.0-0

Then edit jack-audio-connection-kit-0.98.1/debian/rules (or 0.80 or whatever 
yours actually says...  I got 0.98.1 from that command, running Sid) and find 
the bit with -O3 and change it to -O0 then

fakeroot debian/rules binary

Then try installing and running the resulting packages.  If that licks the 
illegal instruction problem, that will mean something to someone who knows a 
lot more about compiler internals than I do.  It will also certainly mean you 
have a legitimate bug to file for the package maintainer to contend with.

-- 
Michael McIntyre  ----   Silvan <dmmcintyr@users.sourceforge.net>
Linux fanatic, and certified Geek;  registered Linux user #243621
http://www.geocities.com/Paris/Rue/5407/
http://rosegarden.sourceforge.net/tutorial/



Reply to: