on 09/20/2007 07:53 PM Aaron Mavrinac wrote the following: > I ran into this problem some time ago on my Ultra 10 running a 2.4 > kernel/profile. I didn't keep any notes, so I'm not 100% sure about > this, but if I recall I came to the conclusion that the 2.4 headers > were the problem and there was just no mask in the 2.4 profile to > prevent the newer, incompatible silo version from emerging. Since the > old one worked fine I just masked all newer versions manually and let > it be. >
I did the same: I masked silo-1.4.13-r1 and tried silo-1.4.13 and it compiled just fine ;-) Thanks. Aggelos. -- [EMAIL PROTECTED] mailing list
