From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Edd Barrett <edd@openbsd.org>
Subject: Re: [dev-context] Luatex 1.09.0 announcement (Mojca Miklavec)
Date: Sun, 28 Oct 2018 08:26:27 +0100 [thread overview]
Message-ID: <CALBOmsZZaj34b0yh+SBsL95-5C1yJzwfqgqGxMtTfaoDhPzq=A@mail.gmail.com> (raw)
In-Reply-To: <20181025110921.GA44056@valencay.home>
Dear Damien,
On Thu, 25 Oct 2018 at 13:09, Damien Thiriet wrote:
>
> LuaJIT did not work on OpenBSD 6.3 texlive* packages.
While it's not super important to have it, there's something super
suspicious about that. It did work until Luigi switched to the
experimental branch:
http://build.contextgarden.net/builders/luatex.openbsd-amd64-6.2.prg/builds/217
and broke immediately after that:
http://build.contextgarden.net/builders/luatex.openbsd-amd64-6.2.prg/builds/222
In TeX Live it broke for me some time ago. I checked the history, but
already the first build for OpenBSD 6.2 had luajittex build disabled
(in April 2018; according to git history I committed the change on the
29th of April 2018). I would say it must have worked in TeX Live 2017,
but I compiled that one with gcc on OpenBSD 6.0/6.1 rather than with
clang. Not that this is a valid excuse though: as shown above, clang
successfully compiled luajittex on OpenBSD 6.2 and 6.3 from the luatex
repository until very recently.
> I can live without it anyway.
> Does this mean that a ConTeXt live install will be available on OpenBSD 6.4?
I was not aware that OpenBSD 6.4 was out until you mentioned it. I'll
upgrade the machine on our build farm.
But just to make sure: did the minimals work correctly for you on 6.3?
> As usual I would be highly interested, even more since I discovered that
> using official packages (TL-2017 btw), you have to load everything to
> get context, since texlive-texmf-full is a texlive-texmf-context dependency.
I would try to talk to Edd or others packaging TeX Live if there's a
way to reduce the dependencies. We can help advise on what is (not)
needed.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2018-10-28 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1540461601.14905.ntg-context@ntg.nl>
2018-10-25 11:09 ` Damien Thiriet
2018-10-25 11:20 ` luigi scarso
2018-10-28 7:26 ` Mojca Miklavec [this message]
2018-10-28 23:04 ` luigi scarso
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='CALBOmsZZaj34b0yh+SBsL95-5C1yJzwfqgqGxMtTfaoDhPzq=A@mail.gmail.com' \
--to=mojca.miklavec.lists@gmail.com \
--cc=edd@openbsd.org \
--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).