Here are a couple experimental observations.

1. Detecting musl.

-- Alpine Linux/sh --

$ ldd --version 2>&1 | grep -F musl

musl libc (x86_64)

$? = 0

-- Debian/bash --

$ ldd --version 2>&1 | grep -F musl

(nothing; $? = 1)

-- Debian/zsh --

$ ldd --version 2>&1 | grep -F musl

(nothing; $? = 1)

A few notes:

a.) On some platforms fgrep has been deprecated (in favour of `grep -F`) so it's not future-proof

b.) The caret (^) passed to `grep -F` will not be interpreted as a regex, since -F forces non-regexp, meaning the '^' will be interpreted literally (and the string "^musl" is not in the ldd output).

c.) It's likely safe to assume that the string 'musl' will only occur in `ldd --version` where musl is installed

d.) I did not test a case Arthur described here https://mailman.ntg.nl/pipermail/ntg-context/2018/091123.html, but the use of -F ought to avoid the zsh EXTENDED_GLOB problem

Based on this, a reasonably portable detection of musl in first-setup.sh and tex/setuptex might be:

if command -v ldd >/dev/null && ldd --version 2>&1 | grep -Fq 'musl' >/dev/null

2. Running /context/first-setup.sh the link /context/bin/texlua did not exist and first-setup.sh fails.

Once symlinked to `luatex` in the same directory, first-setup.sh will run rsync.

3. Similarly /context/tex/texmf-linuxmusl-64/bin/texlua does not exist, so setuptex fails.

Once symlinked `luatex -> texlua` then setuptex can be executed (bearing in mind `setuptex` needs to be updated with the same musl detection test as first-setup.sh)

4. setuptex needs to be called with an explicit directory otherwise it complains with

""/bin" is not a valid TEXROOT path.

(There is no file "/bin/texmf/tex/plain/base/plain.tex")

provide a proper tex root (like '. setuptex /something/tex')"

Running this will run setuptex variables:

$ . /context/tex/setuptex /context/tex

Setting "/context/tex" as ConTeXt root.

5. Running context exits with:

mtxrun | unknown script 'context.lua' or 'mtx-context.lua'

That's as far as I have gotten for now, but I thought this enough to report.

6. I am happy to take direction and report, but it is also straightforward to reproduce with Docker via the Dockerfile:

FROM python:3.6-alpine3.7
RUN apk --no-cache add rsync
WORKDIR /context

Then running docker:

$ docker build -t context .

$ docker run -ti context /bin/sh

Then in the docker container shell, run:

$ cd /context

$ wget http://minimals.contextgarden.net/setup/first-setup.sh \
$ sh ./first-setup.sh --modules=all --engine=luatex

(please pardon the formatting - some copying and pasting here).

I hope this is helpful.

Cheers,

Brian

On Sun, 8 Apr 2018 at 20:52 Henri Menke <henrimenke@gmail.com> wrote:

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).
>
> 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.

Similar to TeX live I have set up an automated Travis CI build, which can deploy
binaries to GitHub releases.
https://github.com/hmenke/luatex/blob/master/.travis.yml

However, I just forked Adam's mirror and I am not planning to keep mine updated.
It would be nice to have some sort of “official” LuaTeX mirror on GitHub for
that. Nevertheless, it might be worthwhile to check the '.travis.yml' I posted
above into the LuaTeX SVN.

>
> >
> > 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
___________________________________________________________________________________