From: Philipp Gesang <phg@phi-gamma.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Simon Dales <simon@getthingsfixed.co.uk>,
Boris Veytsman <borisv@lk.net>, Karl Berry <karl@freefriends.org>
Subject: Re: standalone / setuptex on ARM
Date: Tue, 23 Aug 2016 19:41:07 +0200 [thread overview]
Message-ID: <20160823174107.GA15294@phlegethon> (raw)
In-Reply-To: <CALBOmsYzE_g55NLpgZLjYFOOcbMfFEuumhPRVEKOKHTPyhz-PQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2487 bytes --]
···<date: 2016-08-23, Tuesday>···<from: Mojca Miklavec>···
> The Raspberry PI returns:
>
> $ readelf -A /proc/self/exe
> Attribute Section: aeabi
> File Attributes
> Tag_CPU_name: "6"
> Tag_CPU_arch: v6
> Tag_ARM_ISA_use: Yes
> Tag_THUMB_ISA_use: Thumb-1
> Tag_FP_arch: VFPv2
> Tag_ABI_PCS_wchar_t: 4
> Tag_ABI_FP_rounding: Needed
> Tag_ABI_FP_denormal: Needed
> Tag_ABI_FP_exceptions: Needed
> Tag_ABI_FP_number_model: IEEE 754
> Tag_ABI_align_needed: 8-byte
> Tag_ABI_align_preserved: 8-byte, except leaf SP
> Tag_ABI_enum_size: int
> Tag_ABI_HardFP_use: SP and DP
> Tag_ABI_VFP_args: VFP registers
> Tag_CPU_unaligned_access: v6
>
> and both tests fail (like they are supposed to).
Yep, I tested on one of my Π’s. ;)
> That's great, I'll
> patch the scripts, thank you very much. I was a bit frustrated by the
> inability to support both platforms properly.
> I'm now waiting for the code for the 64-bit arm binaries :)
Can’t help with that directly, I have a Π3 but it’s still running
a 32 bit distro.
> I have one in my drawer that I still need to set up.
>
> > i'll let mojca decide that ... (i just ship what she patches in setuptex)
>
> I'll apply the patch. Now, setuptex is not problematic, the same patch
> goes there. But mtxrun doing its own guesswork on top of this might
> be. Let's see.
>
> And then there's the next question: what hardware/software do we need
> if we want to add an additional unit to our (new) build farm? At the
> moment Boris is kindly providing the binaries, but it would be nice to
> add some small piece of hardware into the cellar that just waits and
> starts building automatically whenever there's a need to do so.
I’ve set up a scratchbox [0] cross build env that produces usable
binaries. Maybe if I manage to get that automated I could provide
the soft-float binary. (I’ve only built Luatex so far, not sure
what else is needed.)
> Taco, Philipp just volunteered for a presentation (with workshop) at
> the ConTeXt Meeting.
> Title: Running ConTeXt (and compiling binaries) on my phone.
The hard part is displaying the PDFs. I’ll be glad to answer
questions but I doubt many would be interested on the oddities of
exotic 7 years old hardware =)
Thanks for including the patch,
Philipp
[0] This one: http://www.scratchbox.org/ -- not \box \scratchbox!
[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 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
___________________________________________________________________________________
prev parent reply other threads:[~2016-08-23 17:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 5:46 Philipp Gesang
2016-08-23 8:44 ` Hans Hagen
2016-08-23 9:15 ` Mojca Miklavec
2016-08-23 9:27 ` Mojca Miklavec
2016-08-23 10:03 ` Mojca Miklavec
2016-08-23 10:53 ` Mojca Miklavec
2016-08-23 11:30 ` luigi scarso
2016-08-23 17:41 ` Philipp Gesang [this message]
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=20160823174107.GA15294@phlegethon \
--to=phg@phi-gamma.net \
--cc=borisv@lk.net \
--cc=karl@freefriends.org \
--cc=ntg-context@ntg.nl \
--cc=simon@getthingsfixed.co.uk \
/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).