From: Jose Luis Arellano <jose.4rellano@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt on linux-armhf
Date: Fri, 5 Aug 2016 19:54:00 -0300 [thread overview]
Message-ID: <CABLfLbC51+Lm52rc20fpBZ9QpS_E6Z4xy=Y+0s0C47xCddQMoA@mail.gmail.com> (raw)
In-Reply-To: <CALBOmsYgd-nY5HAr5nsaWdcDwzng3pkg=DOGWw6Q5YjGVn5mdA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1465 bytes --]
Thanks for the answer Mojca, i will wait.
BTW, this is the version that am using:
ConTeXt Process Management 0.63
current version: 2016.07.18 16:46
2016-08-05 19:44 GMT-03:00 Mojca Miklavec <mojca.miklavec.lists@gmail.com>:
> On 6 August 2016 at 00:19, Jose Luis Arellano wrote:
> > Hi guys, i need some help. I have installed the linux-armhf version of
> > ConTeXt on my android phone via android deploy, the installation was
> smooth
> > but when i try to create any document, it compile fine, but the resulting
> > document seems to be corrupted. You can see the result in the attached
> file.
> > Thanks in advance.
>
> This might be a bit tricky to debug.
>
> I can try to update the binaries to the very latest version (you
> should be able to get them in a few hours), but the binaries are
> currently compiled on Raspberry PI and if Android happens to be
> incompatible to some extent, then I have no clue where to start
> looking.
>
> 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
> ____________________________________________________________
> _______________________
[-- Attachment #1.2: Type: text/html, Size: 2581 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:[~2016-08-05 22:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 22:19 Jose Luis Arellano
2016-08-05 22:44 ` Mojca Miklavec
2016-08-05 22:54 ` Jose Luis Arellano [this message]
2016-08-07 3:31 ` Jose Luis Arellano
2016-08-07 8:21 ` Pablo Rodriguez
2016-08-07 12:14 ` Mojca Miklavec
2016-08-08 4:53 ` Jose Luis Arellano
2016-08-08 7:46 ` Mojca Miklavec
2016-08-08 8:14 ` Henri Menke
2016-08-08 19:16 ` Jose Luis Arellano
2016-08-08 19:42 ` Jose Luis Arellano
2016-08-08 20:29 ` Hans Hagen
2016-08-08 23:09 ` Mojca Miklavec
2016-08-30 0:51 ` Jose Luis Arellano
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='CABLfLbC51+Lm52rc20fpBZ9QpS_E6Z4xy=Y+0s0C47xCddQMoA@mail.gmail.com' \
--to=jose.4rellano@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).