From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: platform/architecture (was: new beta)
Date: Thu, 27 Jan 2011 00:21:56 +0100 [thread overview]
Message-ID: <AANLkTin9yg5C_Yd1p-gzfOyH_DDvj=Krdz2n8ZiwZdBf@mail.gmail.com> (raw)
On Wed, Jan 26, 2011 at 22:16, Taco Hoekwater wrote:
>> Maybe "bash --version" would be more reliable than uname?
>
> If you do something like that, then you may as well do
>
> $ file /bin/ls
Not too useful either ...
> bash --version
GNU bash, version 3.2.48(1)-release (x86_64-apple-darwin10.0)
Copyright (C) 2007 Free Software Foundation, Inc.
> file /bin/ls
/bin/ls: Mach-O universal binary with 2 architectures
/bin/ls (for architecture x86_64): Mach-O 64-bit executable x86_64
/bin/ls (for architecture i386): Mach-O executable i386
However ... this discussion was already being held long ago ... there
is no reason why luatex could not be as smart as "bash --version" is
and aware of the architecture it was compiled for (that is not
necessary the platform it is running on; an obvious case being i386
luatex running on 64-bit Mas OS X for example). Somebody would have to
write some simple code to check for that though.
Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2011-01-26 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 23:21 Mojca Miklavec [this message]
2011-01-27 6:25 ` Taco Hoekwater
2011-01-27 6:39 ` Martin Schröder
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='AANLkTin9yg5C_Yd1p-gzfOyH_DDvj=Krdz2n8ZiwZdBf@mail.gmail.com' \
--to=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
/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).