December 2009 - binary-builders

[Context] [Bug 379146] [NEW] mtxrun
by Mojca Miklavec 11 Jun '11

11 Jun '11

Public bug reported: from Alan BRASLAU, untested I did a fresh install of the minimals today and observed a fleeting, obscure mtxrun bug: $ context myfile did not find the script mtx-context.lua $ mtxrun --script /usr/local/context/tex/texmf-context/\ scripts/context/lua/mtx-context.lua myfile ran fine, as now does all subsequent runs of "context myfile". So something gets initialized, but is not found by default. You will only notice this upon a (totally) fresh install. ** Affects: context Importance: Undecided Status: New -- mtxrun https://bugs.launchpad.net/bugs/379146 You received this bug notification because you are a member of ConTeXt distribution team, which is the registrant for ConTeXt distribution. Status in ConTeXt distribution: New Bug description: from Alan BRASLAU, untested I did a fresh install of the minimals today and observed a fleeting, obscure mtxrun bug: $ context myfile did not find the script mtx-context.lua $ mtxrun --script /usr/local/context/tex/texmf-context/\ scripts/context/lua/mtx-context.lua myfile ran fine, as now does all subsequent runs of "context myfile". So something gets initialized, but is not found by default. You will only notice this upon a (totally) fresh install.

6 8

[Context] 'My' context & luatex domains have moved
by Taco Hoekwater 28 Dec '09

28 Dec '09

Hi all, This regards context.aanhet.net www.metatex.org minimals.metatex.org www.luatex.org tracker.luatex.org The sites in mentioned above have moved to a new hosting server, with IP address 195.12.62.12. This new server has a better net connection and more disk space, and besides, the old server is going to be powerless in a few days anyway. Apart from the changed IP, everything else should function as before. I you notive any new weirdnesses, please drop me a message. Best wishes, Taco

1 0

[Context] pdftosrc and ttf2afm
by Peter Münster 26 Dec '09

26 Dec '09

Hello, After "do_all.sh" I get the following errors: Failures: - copy pdftosrc binaries - copy ttf2afm binaries What should I do? Thanks, Peter -- Contact information: http://pmrb.free.fr/contact/

2 2

[Context] Luatex 0.47.0
by Mojca Miklavec 19 Dec '09

19 Dec '09

Dear builders, the new LuaTeX beta-0.47.0 is not compatible with beta-0.46.0, so it's important to commit the new version of luatex as soon as possible. Please check if ./do_all.sh does the job (apart from compilation problem of pdftex on FreeBSD). Hans - since it seems to be working now - feel free to do svn up and then uncomment "--without-trunk" in do_all.sh and add the script to cron job on the server. Thanks to everyone, Mojca

2 1

[Context] new building scripts (important)
by Mojca Miklavec 19 Dec '09

19 Dec '09

Hello, I have changed the building scripts a bit: - they are now split in several pretty standalone steps: a) fetching sources b) fetching existing binaries from svn c) building d) committing to SVN (not implemented yet) - there is more error checking - if some engine doesn't build, the process may still continue - it's possible to force rebuilding even if versions match - it should be possible to choose which engines to build, but option parsing is not implemented yet - there are many differences that influence Mac OS X building, but you should not bother about them anyway - buiding xetex disabled until we get support for 64-bit - it should be possible to build from any mac (at least in theory) - support for 64-bit architecture and fat binaries now from all the three relevant architectures I did that because there were constant problems when some of the steps failed to work and also because I had to modify the OS X part (why does Mac always need to be an exception? :). You may try to do svn up ./do_all.sh and report back about any problems that you might encounter. I would be grateful for any bug reports. This command will not commit to SVN yet, but there's VERSIONS.new that should be moved to VERSIONS and there is VERSIONS.svn that should be used as commit message, so the last step is almost-trivial to do manually as well, I just need to code it :) Mojca

3 6

[Context] Linux PPC
by Mojca Miklavec 13 Dec '09

13 Dec '09

> OK, running do_all.sh gives > > Error: your system "Linux " is not supported yet, > but we're glad that you would like to provide the binaries for it. > Please ask for instructions on the ConTeXt mailing-list (ntg-context(a)ntg.nl) > > That's why I thought this was exclusively targeted at OS X. And I see Oh, I guess that it's "Linux <empty_string_for_architecture>". Maybe we need to fix that message ... > PLATFORMS="$platform" > if [ $system = 'Darwin' ]; then > PLATFORMS="osx-intel osx-64 osx-ppc osx-universal" > fi No, this only means that if one is working on OS X, it will build binaries for three architectures + universal ones, so the same script runs 4 times in a loop to build them all. $platform string is still not empty. > so I assumed that all the other platforms would be unknown. Or am I missing a newer version of the script? No, you are not, but I never realized that the script doesn't work on your computer. > uname -m: ppc64 > uname -s: Linux OK, so Mac is not the only faulty player here :) OS X tends to say uname -m: i386 while being purely 64-bit system (exactly the contrary). Just curious: does "echo $HOSTTYPE" return anything useful on your system (please try both your shell and bash)? > The minimals work fine, but I don't use setuptex (I use zsh and have my own script that is adapted to my system). If you want, I can try and see if/how I can make it work on linux-ppc. I didn't know that either. That's pretty important piece of information. We can fix that. > As to compatibility between linux-ppc and linux-ppc64: ppc64 is kind of a misnomer. As far as I have understood, only the kernel is 64-bit; the userland is 32-bit. AFAICS, no linux distribution (with the exception of gentoo) has a real 64-bit implementation. So: my system will build 32-bit binaries which should be compatible with all linux-ppc systems. The only question remains: what happens if some gentoo user starts using (or compiling) the binaries? I would not like to make too many problems around it, I would just like to understand, so that we might have a chance to fix it properly (if such a chance exists), else we'll just assume that ppc and ppc64 are equal until someone starts complaining. Mojca

2 2