From: Henri Menke <henrimenke@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Build for Alpine Linux
Date: Fri, 13 Apr 2018 23:42:45 +1200 [thread overview]
Message-ID: <748bec33-fbc7-9aa1-0392-d52e795a0702@gmail.com> (raw)
In-Reply-To: <CALBOmsbGMW-ZXXdWKRaaYYh+4CXikoVrot0NOyw4Ep=s5kxKFA@mail.gmail.com>
On 04/13/2018 11:14 PM, Mojca Miklavec wrote:
> On 11 April 2018 at 22:37, Hans Hagen wrote:
>> On 4/11/2018 10:08 PM, Brian Hunt wrote:
>>
>>> 3. Add texlua (and texluac?) to
>>> a. the setup rsync bin/ directories
>>> b. the tex/texmf-linuxmusl(|-ppc|-64)
>>
>> we don't use texluac, don't need texlua on windows and on linux texlua is
>> just a symlink
>
> This was entirely my fault which has been fixed in the meantime.
>
>> if musl needs different bin then there should be a different initial
>> download i think because basically we're now talking of: windows, osx,
>> linux, linuxmusl (a different species)
>
> 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.
>
>>> 4. Update mtxrun
>>>
>>> Here's code that ought to work for detecting musl in mtxrun. Around line
>>> 3721 of the mtxrun add:
>>>
>>> if find(architecture,"x86_64",1,true) then
>>> platform="linux-64"
>>> elseif find(architecture,"ppc",1,true) then
>>> platform="linux-ppc"
>>> else
>>> platform="linux"
>>> end
>>> + if resultof("ldd --version 2>&1"):find("musl") ~= nil then
>>> + platform = platform:gsub("linux", "linuxmusl")
>>> + end
>>
>>
>> that's not going to happen, some system call 9each run) in order to
>> determine what linux species we run ... (there are a few calls but these are
>> never used becasue we use HOSTTYPE (if needed we can set one ourselves on
>> these platforms)
>>
>> isn't there some magic env var that tels if musl is used? do programs and
>> scripts really have to jumpo through such loops
>
> Hans, we don't really need this code for the sake of minimals
> themselves, it is part of ConTeXt code that needs it and fails.
>
> The problem is that even if I properly detect the platform upfront,
> your code (mtx-update) will refuse to respect the setting. When
> calling
> ./bin/mtxrun --script ./bin/mtx-update.lua --force --update --make
> --context=beta --platform=linuxmusl-64 --texroot="/some/path"
> from musl linux, the mtx-update will insist in always installing and
> using linux-64 binaries even if they don't work, no matter what else
> we try.
>
> I still believe that a string like "x86_64-linuxmusl" is something
> that luatex itself should be able to return when asked about what
> platform it is running on (what platform it has been compiled for).
> We've discussed this with Taco many years ago, but this has never been
> implemented.
>
> 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-04-13 11:42 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 [this message]
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=748bec33-fbc7-9aa1-0392-d52e795a0702@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).