From: Henri <henrimenke@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Support for musl
Date: Tue, 30 Jan 2018 12:23:14 +1300 [thread overview]
Message-ID: <1517268194.26485.87.camel@gmail.com> (raw)
In-Reply-To: <CALBOmsb6_eDZhfShZq-05_ZDmafWpSZpWkGePW1z46zVSduZzQ@mail.gmail.com>
It looks like we are going to get upstream support for musl from TeX live.
There is this extremely long thread on the tlbuild mailing list.
https://tug.org/pipermail/tlbuild/2018q1/003972.html
An automated build on Alpine Linux has been included in the TeX live continuous
integration on GitHub.
https://github.com/TeX-Live/texlive-source/blob/master/.travis.yml
What would I have to do in order to get an automated build for ConTeXt
standalone for musl?
Hans might be interested in detecting musl libc automatically, which I have
recently merged into GNU autotools:
https://git.savannah.gnu.org/cgit/config.git/commit/?id=3d00f60242f1726fc6eaa38e09435a969ee7ebe5
It uses ldd to detect whether musl is used because ldd prints "musl libc" to
stderr.
https://git.musl-libc.org/cgit/musl/tree/ldso/dynlink.c#n1538
On Fri, 2018-01-19 at 12:22 +0100, Mojca Miklavec wrote:
> On 19 January 2018 at 11:40, Henri Menke wrote:
> >
> > Dear list,
> >
> > I'd like to support Linux platforms which use musl (https://www.musl-libc.or
> > g/) instead of glibc, like for instance Alpine Linux.
> >
> > How would I go about this? Can you share existing build scripts for, e.g.
> > Linux-64? Do I have to provide build infrastructure?
> Can you please raise that question on the TeX Live mailing list?
>
> If TL team is not willing to support it, we can still do it ourselves,
> but let's first see if there's an "official" way to support it, also
> with respect to naming.
> We would need to set up a VM running that version of Linux + some
> other stuff (at the moment we are experiencing some technical issues
> with network and the build infrastructure and we need to fix the
> existing issues first, but then we could look into it).
>
> (Would you expect any other use besides you?)
>
> 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
> ______________________________________________________________________________
> _____
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2018-01-29 23:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 10:40 Henri Menke
2018-01-19 11:22 ` Mojca Miklavec
2018-01-19 11:38 ` Henri Menke
2018-01-19 12:33 ` luigi scarso
2018-01-20 3:13 ` Henri Menke
2018-01-21 1:04 ` Henri
2018-01-21 10:53 ` Hans Hagen
2018-01-21 20:49 ` Henri
2018-01-22 2:21 ` Alan Braslau
2018-01-22 6:54 ` Hans Hagen
2018-01-22 8:18 ` luigi scarso
2018-01-22 19:09 ` Andreas Schneider
2018-01-22 20:42 ` Henri
2018-01-29 23:23 ` Henri [this message]
2018-01-31 9:26 ` Mojca Miklavec
2018-01-31 9:36 ` luigi scarso
2018-01-31 9:51 ` Hans Hagen
2018-03-21 14:26 ` Mojca Miklavec
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=1517268194.26485.87.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).