Wolfgang Schuster said the following at 11/24/2009 01:56 PM :

Am 24.11.2009 um 21:52 schrieb D. R. Evans:

...

I'm probably being blind, but I can't find any instructions about downloading the source from svn and building it.

Can some kind person please point me to such instructions? I want to be sure I'm running current code before I file any "this works in pdftex but not in luatex" reports.

server : svn checkout http://foundry.supelec.fr/svn/luatex username: anonymous password:

Are you sure that's right? 2.2GB downloaded so far, and still going strong. I'm going to have to kill the download if it goes on much longer, and re-do it on a larger partition. And if there are any instructions as to what to do with it all, they aren't obvious. Doc -- Web: http://www.sff.net/people/N7DR

Khaled Hosny said the following at 11/24/2009 03:01 PM :

Should be http://foundry.supelec.fr/svn/luatex/trunk or you will download all luatex branchs and tags, which you aren't interested in.

Much better. Building with build.sh gives this error after a few minutes: ---- make[5]: Entering directory `/tmp/luatex/trunk/build/texk/web2c' date >stamp-tangle srcdir=../../../source/texk/web2c /bin/sh ../../../source/texk/web2c/web2c/convert tangleboot gcc -DHAVE_CONFIG_H -I. -I../../../source/texk/web2c -I./.. -I/tmp/luatex/trunk/build/texk -I/tmp/luatex/trunk/source/texk -g -O2 -MT tangleboot.o -MD -MP -MF .deps/tangleboot.Tpo -c -o tangleboot.o tangleboot.c mv -f .deps/tangleboot.Tpo .deps/tangleboot.Po /bin/sh ./libtool --tag=CC --mode=link gcc -g -O2 -o tangleboot tangleboot.o lib/lib.a /tmp/luatex/trunk/build/texk/kpathsea/libkpathsea.la -lm eval: 1: libtool_args+=: not found eval: 1: compile_command+=: not found eval: 1: finalize_command+=: not found eval: 1: libtool_args+=: not found eval: 1: compile_command+=: not found eval: 1: finalize_command+=: not found eval: 1: libtool_args+=: not found eval: 1: compile_command+=: not found eval: 1: finalize_command+=: not found eval: 1: libtool_args+=: not found eval: 1: compile_command+=: not found eval: 1: finalize_command+=: not found eval: 1: libtool_args+=: not found eval: 1: compile_command+=: not found eval: 1: finalize_command+=: not found eval: 1: libtool_args+=: not found eval: 1: libtool_args+=: not found eval: 1: libtool_args+=: not found libtool: link: gcc lib/lib.a /tmp/luatex/trunk/build/texk/kpathsea/.libs/libkpathsea.a -lm lib/lib.a(main.o): In function `main': /tmp/luatex/trunk/build/texk/web2c/lib/../../../../source/texk/web2c/lib/main.c:26: undefined reference to `mainbody' collect2: ld returned 1 exit status ---- FWIW I am on a 64-bit karmic system, fully up to date, with a lot of development-related stuff installed, but I've never tried to build anything related to any kind of TeX on this machine before. I've *used* a lot of Tex stuff on it, but not tried any TeX-related development until now. Presumably the above error is because I'm missing something? Doc -- Web: http://www.sff.net/people/N7DR

Martin Schröder said the following at 11/24/2009 04:34 PM :

2009/11/25 D. R. Evans :

...

Presumably the above error is because I'm missing something?

/bin/sh is probably not a bash. Try to convince the build script to use bash.

I was going to reply "of course it's bash"... but then I looked at the link and found something called dash. I guess I've never noticed before because I always put an explicit "#! /bin/bash" at the start of my shell scripts. So I learned something, which is always good. Thank you. Doc -- Web: http://www.sff.net/people/N7DR

On Tue, Nov 24, 2009 at 04:13:57PM -0700, D. R. Evans wrote:

Khaled Hosny said the following at 11/24/2009 03:01 PM :

...

Should be http://foundry.supelec.fr/svn/luatex/trunk or you will download all luatex branchs and tags, which you aren't interested in.

Much better.

Building with build.sh gives this error after a few minutes:

Doing "export CONFIG_SHELL=/bin/bash" is usually enough, as it forces using bash (no idea why this isn't the default.) Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer

D. R. Evans wrote:

Khaled Hosny said the following at 11/24/2009 05:17 PM :

...

Doing "export CONFIG_SHELL=/bin/bash" is usually enough, as it forces using bash (no idea why this isn't the default.)

Yep, that worked. Thank you very much. I spent about half an hour trying to figure out how to change the shell before I saw your e-mail.

Now to the next question.

The INSTALL file says:

"Post-compilation installation should be a simple matter of copying the executable to a normal place for web2c binaries and generating the desired formats."

This might as well say "... should be a simple matter of executing black magic that you will know if you already know it" :-)

Would anyone care to elaborate on the instructions so that a mere mortal can accomplish this? [I vaguely recall something about generating a format file somewhere around 1984. Ampersands played a part, I think. I'm rambling.]

I'm sorry if I'm missing something obvious that I should already know.

i suggest that you download tex live and consult its manual; generating formats and putting them in the right spot depends on what macro package you use in combination with some distribution in that case it might be a good idea to start with pdftex etc as that has een integrated in distributions for ages (that kind of support is a bit beyond this list) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

I'm sorry if I'm missing something obvious that I should already know.

There's nothing you should already know, but you should be able to look up that information by yourself. Installation and distribution are far beyond the scope of this mailing-list dedicated to LuaTeX developers (and there is a user list, see http://tug.org/mailman/listinfo/luatex). As for your question, you have to understand the basics of kpathsea, the file lookup library used by most implementations of TeX, and web2c, the actual TeX implementation. Documentation should be available as part of your TeX distribution (if you're using TeX Live, use texdoc to locate documentation), and also online. Since you seem to want to use the latest LuaTeX revision without going through any distribution, you will have to build a tiny distribution of your own around LuaTeX that suits your needs. What I've been using for three years in order to test LuaTeX is to have the latest LuaTeX binary in some directory, to place symbolic links pointing to TeX Live's texmf trees two directories higher, and to build the LuaTeX plain format from the directory where the LuaTeX binary resides, using Knuth's original plain.tex file. These days, it's enough to run "./luatex -ini luatex.ini" to generate the format, where luatex.ini contains \input plain \directlua{tex.enableprimitives("", tex.extraprimitives())} \pdfoutput1 \dump You can then use luatex from the directory where it resides. Arthur

D. R. Evans wrote:

Arthur Reutenauer said the following at 11/25/2009 02:58 PM :

...

...

I'm sorry if I'm missing something obvious that I should already know. There's nothing you should already know, but you should be able to look up that information by yourself. Installation and distribution are far beyond the scope of this mailing-list dedicated to LuaTeX developers (and there is a user list, see http://tug.org/mailman/listinfo/luatex).

I was going to try to help with development -- at the very least by filing useful, detailed bug reports but probably by fixing stuff too -- (since I love TeX and have used C++ since before it was called that) but I had no idea that it would be so incredibly complicated just to install a current build in order to make a useful contribution.

I'll go away now. I apologize for interrupting.

if you look at the reguar tex source code base, you will notice that the luatex code base already is much simpler as the pascal -> c conversion is gone for the rest: tex is not just a program, but also macros, fonts, and other resources and normally a distribution takes care of that, including updating formats and those concepts have not changes with luatex (although some aspects like fonts and patterns have) concerning binaries ... right from the start of the luatex project there have always been recent binaries and therefore no need for doing compilation yourself for what it's worth ... many context users use luatex in combination with a luatex aware version of context and updating to the latest greatest is pretty simple due to mostly automated updating of the tree and also quite some architectures are supported; the users' biggest problem might be that they are testing unstable (new) functionality ... so, maybe starting at the binary-generating end of the game without some experience in updating a regular tex tree (including format generation) was not handy; also, having a binary is one thing, using the lua interfaces in luatex is yet another step as texlive ships with the stable version of luatex, why don't you just install tex live 2009; dealing with betas is not a good idea if you are unfamiliar with luatex anyway Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

On Wed, Nov 25, 2009 at 02:29:47PM -0700, D. R. Evans wrote:

Khaled Hosny said the following at 11/24/2009 05:17 PM :

...

Doing "export CONFIG_SHELL=/bin/bash" is usually enough, as it forces using bash (no idea why this isn't the default.)

Yep, that worked. Thank you very much. I spent about half an hour trying to figure out how to change the shell before I saw your e-mail.

Now to the next question.

The INSTALL file says:

"Post-compilation installation should be a simple matter of copying the executable to a normal place for web2c binaries and generating the desired formats."

This might as well say "... should be a simple matter of executing black magic that you will know if you already know it" :-)

Well, I simply do "cp build/texk/web2c/luatex `which luatex`" and then "fmtutil --byfmt luatex" (or better "fmtutil --byengine luatex" for texlive 2009) and let the magic work, though this means I'm left with unstable luatex and no way for the distribution provided version to coexist. -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer