Re: [comp.emacs.xemacs] Package incompatibility

Vin> As the maintainer of the current stable release, I must concur. Steve Vin> Youngs (I know you're out of touch at the moment, perhaps you'll Vin> comment when you get back) please build with the latest stable Vin> release, in this case 21.1. It is a very serious bug if XEmacs 21.2-compiled code can't run on 21.1. I can't reproduce it. Vin> It is now impossible to use M-x calendar. The exact error message I Vin> get when doing M-x calendar is: Vin> invalid lazy-loaded byte code: k��� Vin> The file calendar.elc is generated by XEmacs 21.2 (beta36). It appears Vin> that the output of this byte compiler is not entirely compatible with Vin> XEmacs 21.1.8. I think that's unlikely. What happens if you start up a NEW 21.1.8 xemacs process, and try M-x calendar? I believe there is a bug here, but it is that lazy-loading of bytecode and docstrings does not check the timestamps of updated files, and would happen with any xemacs version. Workaround: shut down your running xemacs and start up a new one. Vin> For pacakges to work, this sort of thing *has* to be avoided. Either Vin> by using separate package directories for separate versions of XEmacs Vin> or by recompiling packages as they are retreived if they are not Vin> precompiled with a compatible version of XEmacs. I agree completely.