Re: Anyone using gcc-3.4 port for audio work?
|--==> Daniel James writes:
DJ> Hi Norval,
>>I chose pure64/sid because there are more pkgs than sarge and it
>>seems to be a little more stable than gcc-3.4.
DJ> I guess the question regarding pure64 vs gcc-3.4 port is: do you want
DJ> to go for maximum possible stability today, or are you developing
DJ> with the future in mind? Further enlightment from people who really
DJ> know the difference would be appreciated!
>>> My first attempt would be to take the DeMuDi kernel source
>>> package and try to build a binary from that, since it's already
>>> got the patches.
DJ> A potential problem here is that the DeMuDi kernel is still based on
DJ> 2.4.x I believe, and I think a lot of the AMD64 work has gone into
DJ> the 2.6.x series instead.
FYI I'm packaging a patched 2.6.10 these days. Let's see how it works..
>>This post came in over the weekend, maybe this could help?
>>I've also booted up with Linux 2.6.10-mm3 that I compiled for the
>>box
DJ> I think there's scope for confusion here. Although some distributions
DJ> use the mm suffix to stand for 'multimedia', it is also the suffix
DJ> used by Andrew Morton to denote his kernel tree. It's further
DJ> complicated by the fact that Andrew has done quite a bit of work on
DJ> multimedia aspects of the kernel, such as low latency. I got confused
DJ> about this myself : )
I'm using the -multimedia suffix, hope it can help in decreasing the entropy :)
Cheers,
Free
Reply to: