ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henri Menke <henrimenke@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Build for Alpine Linux
Date: Mon, 09 Apr 2018 09:26:35 +1200	[thread overview]
Message-ID: <1523222795.18581.21.camel@gmail.com> (raw)
In-Reply-To: <CALBOmsZNeHaR+aQBbSyTUm334_xuAn_OeGVNtMrYyGxn2FiU0w@mail.gmail.com>

On Sun, 2018-04-08 at 22:50 +0200, Mojca Miklavec wrote:
> Dear Brian,
> 
> On 8 April 2018 at 16:56, Brian Hunt wrote:
> > 
> > Hello everyone,
> > 
> > Per this question on tex.StackOverflow, I am having trouble getting ConTeXt
> > (LuaTeX specifically) to run on Alpine Linux:
> > 
> > https://tex.stackexchange.com/questions/425463
> > 
> > Specifically, the build from ConTeXt standalone has a LuaTeX that seems not
> > to run against the musl libc6 library.
> We have a "nearly working" one. At least all the binaries should be
> there, see for example:
>     http://distribution.contextgarden.net/setup/linuxmusl-64/
> 
> There are two to three remaining problems:
> 
> 1.) I disabled automatic musl recognition (short after enabling it)
> after this bug report:
>     https://mailman.ntg.nl/pipermail/ntg-context/2018/091094.html
> I need to finish "parsing"
>     https://mailman.ntg.nl/pipermail/ntg-context/2018/091123.html
> and a few other posts in that thread and maybe make some additional
> testing. There was some "oh no, it has to be the other way around"
> discussion where I no longer followed and I need some more time to
> read everything more carefully (no time for that right now).

This only blows up on Zsh.  I will contact the "config.guess" maintainer (from
where I stole that snippet).

> 
> 2.) Most likely a patch in mtxrun is still needed (but I admit that I
> didn't check) for proper platform recognition. The fact that we are
> struggling in shell doesn't really help doing this part either :)
> 
> 3.) Ideally we need to set up some automated LuaTeX builds to be able
> to get the latest LuaTeX binaries in the future.
> 
> > 
> > Has anyone run ConTeXt on Alpine?
> At the moment it should work if you install TeX Live 2018 pretest with
> the ConTeXt scheme or if you fiddle a bit with the installation (you
> need to hardcode the platform name in first-setup.sh and then still
> some minor things might still go wrong, not sure). But in fact very
> little is required to fix the remaining issues.
> 
> Can you please remind us to pick this up again in a couple of days?
> 
> In the meantime, if you are willing to do some more extensive testing
> of patches (see full thread linked above) on both musl & non-musl
> linuxes, in various shells etc., as well as perhaps come up with a
> patch for mtxrun, that might help.
> 
> 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2018-04-08 21:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-07 21:04 double followtokens? Pablo Rodriguez
2018-04-07 21:25 ` Hans Hagen
2018-04-07 22:11   ` Pablo Rodriguez
2018-04-08 14:41     ` Hans Hagen
2018-04-08 14:56       ` Build for Alpine Linux Brian Hunt
2018-04-08 20:50         ` Mojca Miklavec
2018-04-08 21:09           ` Arthur Reutenauer
2018-04-08 21:26           ` Henri Menke [this message]
2018-04-08 21:45             ` Arthur Reutenauer
2018-04-09  0:50           ` Henri Menke
2018-04-09 18:59             ` Brian Hunt
2018-04-09 19:35               ` Arthur Reutenauer
2018-04-10 11:05                 ` Brian Hunt
2018-04-10 12:26                   ` Brian Hunt
2018-04-10 16:27                   ` Alan Braslau
2018-04-10 20:55                   ` Arthur Reutenauer
2018-04-11 12:30                     ` Brian Hunt
2018-04-11 20:08                       ` Brian Hunt
2018-04-11 20:24                         ` Aditya Mahajan
2018-04-11 20:37                         ` Hans Hagen
2018-04-11 21:08                           ` Brian Hunt
2018-04-13 11:14                           ` Mojca Miklavec
2018-04-13 11:42                             ` Henri Menke
2018-04-13 19:54                               ` Henning Hraban Ramm
2018-04-13 20:02                                 ` Aditya Mahajan
2018-04-13 12:49                             ` Hans Hagen
2018-04-11 23:13                         ` Henri Menke
2018-04-13 10:37                           ` Brian Hunt
     [not found]                             ` <CALBOmsaXyTXhR=j6Ht1LwKGcfxMD4sHjQnEOxtjH-4gc3b5R8g@mail.gmail.com>
     [not found]                               ` <20180417152547.GA1755070@phare.normalesup.org>
2018-04-17 15:54                                 ` Thomas A. Schmitz
2018-04-08 18:10       ` double followtokens? Pablo Rodriguez
2018-04-08 21:17         ` Hans Hagen
2018-04-09 18:25           ` Pablo Rodriguez
2019-01-01 18:17       ` Hans van der Meer
2019-01-01 20:17         ` Hans Hagen

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=1523222795.18581.21.camel@gmail.com \
    --to=henrimenke@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).