ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marco <netuse@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: Minimals fail to install on SunOS x86
Date: Fri, 17 Sep 2010 15:59:01 +0200	[thread overview]
Message-ID: <20100917155901.4ba43842@vorbis> (raw)
In-Reply-To: <AANLkTim1bJM7KTe8kBw+JrDbbJ=WrKo3iyhO6j1oq06C@mail.gmail.com>

On Fri, 17 Sep 2010 10:54:26 +0200, Mojca Miklavec
<mojca.miklavec.lists@gmail.com> wrote:

> For Solaris Sparc we have nobody to compile the binaries at the moment.
I also have a Sparc server but I cannot remote access it from my location now.
But I feel no need to run context on the Sparc.

> The person who asked us for adding Solaris x86 support is not
> using Solaris any more, in last month there was no single Solaris user
> downloading the minimals and after Oracle overtake, I have been
> seriously considering removing support for solaris.
> 
> However, if there is demand for it, we can keep it.
OK. If I'm the only user it's not that important to make it run just for me.

> The question is: is these because there's LuaTeX beta-0.61.0 instead
> of the latest LuaTeX available or is it because my virtual machine
> (OpenSolaris whatever-version-has-been-available-two-months-ago) and
> your server "incompatible" in some sense? I suspect that it is the
> second.
> 
> If you are willing to help us debug, I can try to send you unstripped
> binary.
I will help as much as I can. I did some investigation. The results:

I cannot execute the provided binaries, maybe you're right and the systems are
incompatible. I downloaded the luatex trunk and compiled the source. I can
successfully execute the compiled binary. After having a look at the
first-setup.sh script I performed the mtxrun ... line. As expected it failed
(as I cannot execute the binaries). I replaced the luatex binary with the
fresh compiled one and checked the other programs. Result: I can execute all
binaries exept luatex and pdftex. Since I only use MkIV this should not be a
problem.

So I made the formats and compiled my test document. MkIV works (including
metapost).

So finally I can get a running system by myself. I will write my own
»first-setup.sh« to update my system.

- To update the system I can use the following command, right?
  mtxrun --verbose --script ./bin/mtx-update.lua --force --engine=luatex
  --texroot=$PWD/tex --extras=all

- After replacing the »buggy« luatex I make the formats using:
  mtxrun --verbose --script ./bin/mtx-update.lua --make --force
  --engine=luatex --texroot=$PWD/tex

Please correct me if I use the wrong arguments. I don't really understand the
use of all the options.

How can I check the luatex version used in the minimals? Maybe it is saved
in some text file. Background: If the luatex version changes my script needs
to fetch the new trunk, compile and replace the »buggy or incompatible«
binary. Simply getting the binary and execute --version triggers the error
mentioned before.

Thanks for your help. If I can do anything (send binaries, etc.) let me know.

best regards
Marco


___________________________________________________________________________________
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:[~2010-09-17 13:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-17  2:09 Marco
2010-09-17  8:54 ` Mojca Miklavec
2010-09-17 13:59   ` Marco [this message]
2010-09-17 16:22     ` Mojca Miklavec

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=20100917155901.4ba43842@vorbis \
    --to=netuse@lavabit.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).