>> At least in TC 4.0.4 > >Oh, ok, I understand now. Yes, there's a chicken and egg problem with >4.0.4. The binaries for Coyote are actually committed in the CVS to >avoid it.
That's why I added a condition to copy. >In HEAD, it works good, OTOH, because it actually follows the build >sequence you suggested. In HEAD 4.0 or 4.1 ? Without my patch, there is still an unconditional copy of coyote -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
