[tex-k] [tlbuild] links changed in running installation after cross-compiling?
mpg at elzevir.fr
Wed Apr 28 19:53:07 CEST 2010
[I wanted to cc tex-k but used the wrong adress, sorry]
Le 28/04/2010 19:50, Manuel Pégourié-Gonnard a écrit :
> Le 28/04/2010 14:04, Manuel Pégourié-Gonnard a écrit :
> > [links changed in host installation after mingw cross-build]
>> So, I would suspect a problem with texlinks or the way it is called
>> during cross-compilation.
> Well, instead of doing wild guesses I should have checked the log, since
> it makes it quite clear that texlinks is indeed the culprit:
> export PATH; /home/mpg/tl/source/inst/bin/i586-pc-mingw32/texlinks -v -f
> /home/mpg/tl/source/inst/texmf/web2c/fmtutil.cnf -e ".exe"
> ln -s aleph.exe /home/mpg/tl/trunk/Master/bin/x86_64-linux/lamed
> ln -s pdftex.exe /home/mpg/tl/trunk/Master/bin/x86_64-linux/amstex
> Now, home/mpg/tl/trunk/Master/bin/x86_64-linux is obviously the wrong
> place to install the symlink :-)
> The problem is, when cross-compiling, prepending the new bin dir to the
> PATH is not enough to make sure texlinks will be working in this dir,
> the new bin dir should be passed explicitly as an argument.
> Also, once forced to work in the correct bindir, texlinks incorrectly
> complains that engines do not exist, since it fails to append $exeext
> during the test.
> I believed I fixed both of these problems in rev 18035. (Tested by doing
> a mingw cross-build and a normal build.)
More information about the tex-k