[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#617378: initialization file `/usr/lib/xindy/xindy.mem' was not created by this version of CLISP runtime

reassign 617378 clisp,xindy
found    617378 clisp/1:2.49-3
found    617378 xindy/2.4-1

On Tue, Mar 08, 2011 at 03:40:42PM +0100, Agustin Martin wrote:
> Package: xindy
> Version: 2.4-1
> Severity: normal
> Hi, J?rg,
> Seems that #580762 is back with new clisp version,
> /usr/lib/clisp-2.49/base/lisp.run: initialization file `/usr/lib/xindy/xindy.mem' was not created by this version of CLISP runtime
> Probably clisp-fasl-loader was not updated.

Hi, Joerg and clisp maintainers,

I am reassigning this bug report to both clisp and xindy simultaneously
because I think this may need action from both sides and surely benefits
from common discussion.

A summary for clisp maintainers, 

xindy depends on clisp-fasl-loader-20080430, provided by clisp-2.49 and
clisp-2.48. This change by J?rg Sommer fixed above problem for 

However, this problem has reappeared with upgrade to clisp-2.49. Both
clisp-2.48 and clisp-2.49 Debian packages provide
clisp-fasl-loader-20080430, so ABI should be compatible. But above error
seems to guess that an ABI change was introduced without bumping
LISPOBJ(version..) in src/constobj.d (By the way, this was changed again
on 6 Aug 2010 after 2.49 release, see hg#15040).

By the way, rebuilding xindy package against clisp 2.49 makes xindy work

If the above is true, Debian clisp should change LISPOBJ(version..) and
xindy should be rebuilt against new clisp to make sure it inherits proper

What do you think is happening? And what should be done?

Of course, there is also the dirty approach of just rebuild xindy and



Reply to: