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
But I have no idea if there is some simple way to hardcode the target
architecture into LuaTeX itself.
You could check the first few bytes of the LuaTeX binary itself, it has to
tell you something about the architecture it was compiled for. That's what
file uses in most cases anyway (the
2009/11/19 Taco Hoekwater t...@elvenkind.com:
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).
How about exposing uname(2)? Or is that
Martin Schröder wrote:
2009/11/19 Taco Hoekwater t...@elvenkind.com:
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).
How about
If I update the minimals via first-setup.sh I get the 32bit-binaries (luatex)
although I'm on Snow Leopard. If I change the binaries myself it works fine
and the compilation is notable faster!
Andreas,
Can you please try one thing?
In first-setup.sh you can try to add the following lines
OK, I did a nasty thing. I have patched setuptex to run 64-bit
binaries on Snow Leopard.
There is only one problem: mtxrun doesn't know that one is running on
a 64-bit platform and consequently fetches just 32-bit binaries.
Consequently one needs to call mtx-update with --platform=osx-64. I
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).
Best wishes,
Taco
On Mon, Nov 16, 2009 at 11:33, Andreas Harder wrote:
Hi all!
If I update the minimals via first-setup.sh I get the 32bit-binaries (luatex)
although I'm on Snow Leopard. If I change the binaries myself it works fine
and the compilation is notable faster!
We had a lengthy discussion about
Mojca Miklavec wrote:
On Mon, Nov 16, 2009 at 11:33, Andreas Harder wrote:
Hi all!
If I update the minimals via first-setup.sh I get the 32bit-binaries (luatex)
although I'm on Snow Leopard. If I change the binaries myself it works fine and
the compilation is notable faster!
We had a
Hans Hagen wrote:
Mojca Miklavec wrote:
On Mon, Nov 16, 2009 at 11:33, Andreas Harder wrote:
Hi all!
If I update the minimals via first-setup.sh I get the 32bit-binaries
(luatex) although I'm on Snow Leopard. If I change the binaries
myself it works fine and the compilation is notable
On Tue, Nov 17, 2009 at 17:16, Taco Hoekwater wrote:
Hans Hagen wrote:
Mojca Miklavec wrote:
On Mon, Nov 16, 2009 at 11:33, Andreas Harder wrote:
Hi all!
If I update the minimals via first-setup.sh I get the 32bit-binaries
(luatex) although I'm on Snow Leopard. If I change the binaries
Mojca Miklavec wrote:
The software test:
Yue:context yue$ if test `uname -r|cut -f1 -d.` -ge 10 ; then
echo yes; else echo no; fi
yes
hm, we need to use the methods built in luatex
Someone should check what is returned in the os.uname() return table.
Mine returns
t={
[machine]=x86_64,
Hi all!
If I update the minimals via first-setup.sh I get the 32bit-binaries (luatex)
although I'm on Snow Leopard. If I change the binaries myself it works fine and
the compilation is notable faster!
Greetings
Andreas
13 matches
Mail list logo
