From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Build for Alpine Linux
Date: Fri, 13 Apr 2018 16:02:34 -0400 (EDT) [thread overview]
Message-ID: <alpine.OSX.2.20.1804131601050.28851@nqv-znpobbx> (raw)
In-Reply-To: <2FE6AE12-3263-4868-A655-6D5C584245AE@fiee.net>
On Fri, 13 Apr 2018, Henning Hraban Ramm wrote:
> Am 2018-04-13 um 13:42 schrieb Henri Menke <henrimenke@gmail.com>:
>
>>> Exactly. We have that. And most bits and pieces are in place to allow
>>> that, except for the problem with mtxrun not being able to determine
>>> the platform correctly.
>>
>> Actually, the musl detection only has to be peformed for downloading
>> binaries. Once those binaries are installed, they behave exactly like
>> the linux-64 binaries. I would suggest to simply drop musl binaries in
>> the texmf-linux-64 folder as well. (Who has ConTeXt for multiple
>> platforms on their computer anyway?) That would render all the funny
>> business of calling ldd in mtxrun superfluous.
>
> Probably only a few people need different binaries, but think of e.g.
> - universities etc. that provide a (SMB/DAV) shared installation on a server
> - dual-boot computers (Windows/Linux or OSX/Windows) that use a shared installation
But the question is for multiple libc runtimes in linux. So, I think that
simply installing the musl and glibc in the same directory is ok.
Aditya
___________________________________________________________________________________
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-04-13 20:02 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
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 [this message]
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=alpine.OSX.2.20.1804131601050.28851@nqv-znpobbx \
--to=adityam@umich.edu \
--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).