From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Yue Wang <yuleopen@gmail.com>
Subject: Re: osx-64-binaries/minimals
Date: Tue, 17 Nov 2009 16:05:46 +0100 [thread overview]
Message-ID: <6faad9f00911170705u1065281fme0c358483e24aba7@mail.gmail.com> (raw)
In-Reply-To: <BA5621BF-4BE0-4292-97FD-B03984E2F18A@uni-koblenz.de>
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 Snow Leopard. The last message was
Yue Wang's proposal to check for 64-bit compatibility:
> The hardware test:
> Yue:context yue$ if test `sysctl -n hw.cpu64bit_capable | grep -c 1` = 1 ; then echo yes; else echo no; fi
> yes
>
> The software test:
> Yue:context yue$ if test `uname -r|cut -f1 -d"."` -ge 10 ; then echo yes; else echo no; fi
> yes
This test needs to be fixed in:
- first-setup.sh
- setuptex
- mtxrun.lua
The biggest problem is the latest one. I'm not sure if Hans is willing
to implement that in MKIV and I'm still not decided if I want to mess
with that ugly code or not.
The reason for the change:
- a bit faster and a bit more puristic
The reason against the change:
- a bit ugly
- the 32-bit binaries work
- one can always boot in 64-bit mode
There's always a third option to provide fat binaries, but as others
would probably confirm: they are a bit fat indeed. Three times the
original size since we now support 3 platforms.
Any other votes?
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 prev parent reply other threads:[~2009-11-17 15:05 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 ` Mojca Miklavec [this message]
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 ` osx-64-binaries/minimals Taco Hoekwater
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=6faad9f00911170705u1065281fme0c358483e24aba7@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.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).