[tlbuild] pdftex bug in luatex?

[Joachim Schrod]

Reinhard Kotucha writes:
> Vladimir Volovich writes:
>  > "NP" == Norbert Preining writes:
>  > 
>  >  NP> luatex and xindy.mem: Please advise!
>  > 
>  > no need to update xindy.mem: it changes with every build (even if the
>  > sources did not change; don't know why).

xindy.mem is a memory dump of CLISP's byte code, much like a .fmt file
for TeX. This file *is* the xindy *executable*, xindy.run is "just"
the CLISP run time engine that executes the byte code. xindy.mem is
produced by the CLISP function saveinitmem which is akin to \dump in
TeX.

I don't know what saveinitmem does internally and why it produces a
different file every time. Probably it really includes time stamp of
production, but then it is not something that the xindy source itself
triggers. If it does so, it is an inherent feature of CLISP that one
cannot turn off, to my knowledge -- there is no argument to that
function that changes its behaviour in that regard.

> So far so good.  In order to find out whether this little test is
> sufficient to find out whether xindy and xindy.mem are consistent, I
> removed a byte from xindy.mem and tried again.  No error message.
> Xindy didn't recognize that xindy.mem was broken. 

Do you really expect that? That's just like you can remove a byte from
an .fmt file and TeX will most often not complain either (if you
didn't remove some magic number or damage some pointer structure). You
can remove a byte from many compiled programs or object files and the
loader will not complain.

> Are there time stamps in xindy.mem?  Inserting time stamps is not a
> good idea because even if two files are otherwise identical, programs
> like cmp or diff will always claim that they are different.

As written above, I don't know if there are time stamps in this
compiled program; but that would not be uncommon. Some compilers
record the time of compilation in the produced object or executable
file.

What's the actual problem that you have and want to solve? Maybe I can
help to achieve that in different ways, or I can address the CLISP
folks and ask them for help.

Best,
	Joachim

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Joachim Schrod			Email: jschrod at acm.org
xindy maintainer		http://www.xindy.org/
Roedermark, Germany