Once upon a time, Roi wrote :
> Same as in mplayer src package
> the --with and --without not working correctly
> I do --without arts and it still want to install with arts
This time the problem seems to be that I overestimated xine-lib's configure
script as it seems that it doesn't support disabling arts... so if you have
arts-devel installed, its support will be compiled in :-/
Also, I had made another mistake and added the configure option to disable
lirc ot xine-lib when it should have been for xine-ui.
All this is fixed in the upcoming "fr6" release.
Matthias
--
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Red Hat Linux release 7.3 (Valhalla) running Linux kernel 2.4.18-10
Load : 0.08 0.15 0.11, AC on-line, battery charging: 100% (1:47)
_______________________________________________
RPM-List mailing list <RPM-List@freshrpms.net>
http://lists.freshrpms.net/mailman/listinfo/rpm-list

[Neale Pickett]
> ...
> If you can spare the memory, you might get better performance in this
> case using the pickle store, since it only has to go to disk once (but
> boy, does it ever go to disk!)  I can't think of anything obvious to
> speed things up once it's all loaded into memory, though.
On my box the current system scores about 50 msgs per second (starting in
memory, of course).  While that can be a drag while waiting for one of my
full test runs to complete (one of those scores a message more than 120,000
times, and trains more than 30,000 times), I've got no urge to do any speed
optimizations -- if I were using this for my own email, I'd never notice the
drag.  Guido will bitch like hell about waiting an extra second for his
50-msg batches to score, but he's the boss so he bitches about everything
<wink>.
> That's profiler territory, and profiling is exactly the kind of
> optimization I just said I wasn't going to do :)
I haven't profiled yet, but *suspect* there aren't any egregious hot spots.
5-gram'ing of long words with high-bit characters is likely overly expensive
*when* it happens, but it doesn't happen that often, and as an approach to
non-English languages it sucks anyway (i.e., there's no point speeding
something that ought to be replaced entirely).