thank you for the patch WK I'll try it in my next build - strange as it seems even with the errors mentioned above, all the CS tests seems to work fine so I'm a little confused about what feature of CS this could affect.
A purist might say that this isn't a bug in crystal space, but rather the implementation of cal3d changed. However, I say that since the instructions are to download the latest cal3d, rather than a specifc cal3d, the fact that crystal space aims at a moving target and misses, crystal space still misses it's target. If they didn't want to aim at a moving target, they should have specified which version to download, or offer a working version on this site.
I strongly feel the same as you - the solution is indeed to flank to each CS source distribution the sources known to work with that CS release as for the mandatory as for a set of the suggested packages (ode,cal3d etc...)