ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: linux binaries split?
Date: Sat, 24 Mar 2018 13:57:21 +0100	[thread overview]
Message-ID: <26349f25-e341-c550-6de3-17b16f6f8fcb@uni-bonn.de> (raw)
In-Reply-To: <CALBOmsbO-P1pp5jAjPnLRF=ZJHECKfGMKE9f6shP=NZqQ06PTQ@mail.gmail.com>

On 24.03.2018 13:32, Mojca Miklavec wrote:
> The binaries were requested (and provided) by Henri Menke:
>     https://mailman.ntg.nl/pipermail/ntg-context/2018/090611.html
> 
>  From what I understood (maybe I misunderstood) the regular linux
> binaries would not even work on machines with musl, but maybe you have
> both libc and musl installed?
> 
> It was not meant to be a short-term thing (unless/until we figure out
> that there are too many problems with it and nobody uses it), but it
> was probably never even tested properly and Hans did not yet implement
> support in mtxrun, so maybe installing out-of-the-box would not yet
> work, I don't have a machine to test it.

I was just writing this message when more replies arrived.  I have never 
heard of musl and have never installed it; pretty sure all my linux 
installations are regular ones with libc. So: the problem appears to be 
with the test in

if command -v ldd >/dev/null && ldd --version 2>&1 | grep -q ^musl
	then
		libc=musl
	else
		libc=glibc
	fi

which appears to default to musl even if it is not present. But I don't 
know enough about shell scripting to debug it - could it also be a 
problem with the shell used? (Mine is zsh.)

Thomas
___________________________________________________________________________________
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-03-24 12:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-24 10:59 Thomas A. Schmitz
2018-03-24 11:14 ` luigi scarso
2018-03-24 12:30   ` Thomas A. Schmitz
2018-03-24 12:40     ` Hans Hagen
2018-03-24 12:40     ` Mojca Miklavec
2018-03-24 12:43       ` Hans Hagen
2018-03-24 11:15 ` Hans Hagen
2018-03-24 11:26 ` Hans Hagen
2018-03-24 12:32 ` Mojca Miklavec
2018-03-24 12:42   ` Hans Hagen
2018-03-24 12:57   ` Thomas A. Schmitz [this message]
2018-03-24 13:06     ` Arthur Reutenauer
2018-03-24 13:16       ` Thomas A. Schmitz
2018-03-24 16:44         ` Arthur Reutenauer
2018-03-24 16:51           ` Mojca Miklavec
2018-03-24 17:05             ` Thomas A. Schmitz
2018-03-24 18:10               ` Arthur Reutenauer
2018-03-24 23:55                 ` Arthur Reutenauer
2018-03-25 16:24               ` Arthur Reutenauer
2018-03-24 17:36             ` luigi scarso
2018-03-24 17:43               ` Mojca Miklavec
2018-03-24 17:47                 ` luigi scarso
2018-03-24 21:53                   ` Henri Menke
2018-03-24 23:30                     ` Arthur Reutenauer

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=26349f25-e341-c550-6de3-17b16f6f8fcb@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.de \
    --cc=mojca.miklavec.lists@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).