On Thu, Nov 19, 2009 at 07:59, Taco Hoekwater wrote:
> Mojca Miklavec wrote:
>> Hans, Taco - does LuaTeX itself know if it's 64-bit or not?
> Only internally at the moment, but I could add a variable
> in the os library (after I figure out which of the sizeof()'s
> is the best one to use).

When outside the binary one can run "file" for example:

> file osx-intel/current/luatex/beta-0.45.0/luatex
osx-intel/current/luatex/beta-0.45.0/luatex: Mach-O executable i386

> file osx-ppc/current/luatex/beta-0.45.0/luatex
osx-ppc/current/luatex/beta-0.45.0/luatex: Mach-O executable ppc

> file osx-64/current/luatex/beta-0.45.0/luatex
osx-64/current/luatex/beta-0.45.0/luatex: Mach-O 64-bit executable x86_64

> file linux/current/luatex/beta-0.44.0/luatex
linux/current/luatex/beta-0.44.0/luatex: ELF 32-bit LSB executable,
Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked
(uses shared libs), stripped

> file linux-64/current/luatex/beta-0.44.0/luatex
linux-64/current/luatex/beta-0.44.0/luatex: ELF 64-bit LSB executable,
x86-64, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked
(uses shared libs), stripped

But I have no idea if there is some simple way to hardcode the target
architecture into LuaTeX itself. (Apart from compiling "hello world",
running "file" on it, doing a platform-dependent regular expression
and passing that value to luatex at compile time. But that would be
really really ugly.)

gcc could be as kind as returning the architecture on request.

Yes, I know, I should be dreaming at night, not in the middle of day.
If your question is of interest to others as well, please add an entry to the 

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net

Reply via email to