This issue keeps coming up, and every time it gets resolved by re-adding the build dependencies to mcvs that should have been declared by clisp-dev. The weird thing is that looking at clisp-dev's dependencies, the libraries you mention are indeed already specified by clisp-dev. So why do the autobuilders not install them when asked to build mcvs?
I could keep adding the required build dependencies to my package but I would very much like to know why they are necessary in the first place. The gcc-3.3 dependency is not declared by mcvs explicitly, so I suspect that perhaps clisp pulls it in without declaring a proper Depends: gcc-3.3 [sparc] line. Any ideas? - Robin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
