From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: Kip Warner <kip@thevertigo.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Unsupported Platform
Date: Mon, 8 Aug 2011 22:53:34 +0200 [thread overview]
Message-ID: <CALBOmsYbqxoELyj=jrNGN93FvxOYk_VJrPzH2gh51NL5UBmyig@mail.gmail.com> (raw)
In-Reply-To: <1312835621.3064.101.camel@kip-laptop>
On Mon, Aug 8, 2011 at 22:33, Kip Warner wrote:
> On Tue, 2011-06-14 at 09:56 +0200, Mojca Miklavec wrote:
>> I will keep your offer in mind in case that a few more people request
>> support for the same architecture. If you change your mind and want to
>> start building, just let me know.
>>
>> Mojca
>
> Hey Mojca. Sorry for resurrecting a dead thread, but I've been curious
> lately as to why ConTeXt isn't already natively running under mipsel.
> The reason I ask is because, as I understand it, the backbone of
> ConTeXt is Lua which runs everywhere?
Lua may run everywhere in the sense that you can compile it anywhere,
but somebody still has to compile it.
For running ConTeXt you also need LuaTeX; just lua is not enough.
There are great chances that LuaTeX compilation works out of the box
on your machine, but you (or anyone else) still need to compile it.
I don't have mips64 architecture. If you want to run it, you need to
compile it yourself.
(Alternatively you could grant ssh access to somebody else to do it
instead of you.)
After that I have no problem including general support for any other
user on the same architecture, but I cannot do anything without
appropriate machine.
Setting everything up should not take more than one hour, but in case
of bugs it might take time to resolve them. Once you have everything
set up, it only takes a minute to run a script (and 10 minutes for
your computer to finish compilation + some time to upload result), but
you need to do it for every LuaTeX release without too long delays.
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:[~2011-08-08 20:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 23:42 Kip Warner
2011-06-13 7:34 ` Mojca Miklavec
2011-06-13 16:51 ` Kip Warner
2011-06-13 17:37 ` Mojca Miklavec
2011-06-14 1:08 ` Kip Warner
2011-06-14 7:56 ` Mojca Miklavec
2011-06-14 19:26 ` Kip Warner
2011-08-08 20:33 ` Kip Warner
2011-08-08 20:53 ` Mojca Miklavec [this message]
2011-08-08 20:59 ` Kip Warner
2011-06-14 10:48 ` Stappers
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='CALBOmsYbqxoELyj=jrNGN93FvxOYk_VJrPzH2gh51NL5UBmyig@mail.gmail.com' \
--to=mojca.miklavec.lists@gmail.com \
--cc=kip@thevertigo.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).