ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Yue Wang <yuleopen@gmail.com>
Subject: Re: osx-64-binaries/minimals
Date: Wed, 18 Nov 2009 07:31:52 +0100	[thread overview]
Message-ID: <4B0394D8.8010005@elvenkind.com> (raw)
In-Reply-To: <6faad9f00911170833ge8e6452hed23722d2c982fe3@mail.gmail.com>

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",
>  ["nodename"]="...[my ip]...",
>  ["release"]="10.0.0",
>  ["sysname"]="Darwin",
>  ["version"]="Darwin Kernel Version 10.0.0: Fri Jul 31 22:46:25 PDT
> 2009; root:xnu-1456.1.25~1/RELEASE_X86_64",
> }
> 
> but I'm booting in 64-bit mode (I need to reboot first to check for
> return value in 32-bit mode).
> 
> On one hand uname doesn't return anything usable when booting with
> 32-bit kernel, but on the other hand one probably already runs the
> 64-bit luatex at the time when mtxrun needs to determine the
> architecture.

Well, I doubt you can discover whether you have a totally 32bit software
environment with a 64bit kernel without lots of trickery (but I could
be wrong about that). In any case, os.uname() will give the same results
as the shell command uname.

64bit osx runs 32bit executables (I assume) so you could make the
initial luatex (the one used during install) be a 32bit one, then make
that one decide on which one to use for normal typesetting?

Best wishes,
Taco


___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

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	other threads:[~2009-11-18  6:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.448.1258320461.22155.ntg-context@ntg.nl>
2009-11-15 22:15 ` Indent missed after \placefigure[inner] Vyatcheslav Yatskovsky
2009-11-16 10:13   ` Wolfgang Schuster
2009-11-16 10:33     ` osx-64-binaries/minimals Andreas Harder
2009-11-17 15:05       ` osx-64-binaries/minimals Mojca Miklavec
2009-11-17 15:44         ` osx-64-binaries/minimals Hans Hagen
2009-11-17 16:16           ` osx-64-binaries/minimals Taco Hoekwater
2009-11-17 16:33             ` osx-64-binaries/minimals Mojca Miklavec
2009-11-18  6:31               ` Taco Hoekwater [this message]
2009-11-18 12:49       ` osx-64-binaries/minimals Mojca Miklavec
2009-11-19  1:18         ` osx-64-binaries/minimals Mojca Miklavec
2009-11-19  6:59           ` osx-64-binaries/minimals Taco Hoekwater
2009-11-19  8:43             ` osx-64-binaries/minimals Mojca Miklavec
2009-11-19  8:53               ` osx-64-binaries/minimals Arthur Reutenauer
2009-11-19 18:19             ` osx-64-binaries/minimals Martin Schröder
2009-11-20  7:09               ` osx-64-binaries/minimals Taco Hoekwater
2009-11-15 22:19 ` Indent missed after \placefigure[inner] Vyatcheslav Yatskovsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B0394D8.8010005@elvenkind.com \
    --to=taco@elvenkind.com \
    --cc=ntg-context@ntg.nl \
    --cc=yuleopen@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).