From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: [NTG-context] update
Date: Mon, 8 Jan 2024 11:36:19 +0100 [thread overview]
Message-ID: <462b1f2c-3721-44ae-8aa4-af4010b5c6cd@freedom.nl> (raw)
Hi,
With the build farm still down I now use an alternative build, that is,
I run a compile script on s bunch of machines and hope for the best.
In the process I decided to drop 32 bit installers (users can generate
bins themselves if needed). I also drop bsd version and just use the
latest. For OSX I use a retired macbook air that Hans vd Meer sent me
that has an old operating system but new enough so that its xcode can
make intel and arm binaries. The linux binaries have teh problem that
they depend on glibc versions and I'm assuming a reasonable up to date
system so I use opensuse leap (which is not even that new with it comes
to glibc but we use it on servers here).
texmf-win64 : laptop (linux subsystem on windows)
texmf-windows-arm64 : laptop (native visual studio)
texmf-linux-64 : linux-opensuse-leap (latest leap 15)
texmf-linux-aarch64 : raspberrypi (latest debian)
texmf-linuxmusl-64 : linux-alpine-64 (whatever)
texmf-osx-64 : airbook/118/hvdm (older xcode)
texmf-osx-arm64 : airbook/118/hvdm (older xcode)
texmf-freebsd-amd64 : openbsd-amd64-14 (latest)
texmf-openbsd-amd64 : openbsd-amd64-74 (latest)
If your platform doesn't work you can download the texmf.zip,
context-texmf.zip and installation.pdf and start from there: create the
tree, compile from source, move the binaries and it should just work.
I have no clue if the uploaded files are working but let's see ... (some
paths have been renamed)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2024-01-08 10:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 10:36 Hans Hagen via ntg-context [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-11 17:48 Hans Hagen
2023-06-04 17:01 Hans Hagen via ntg-context
2023-04-26 21:55 Hans Hagen via ntg-context
2023-04-26 23:54 ` Jairo A. del Rio via ntg-context
2023-04-27 2:25 ` Rik Kabel via ntg-context
2023-04-27 2:34 ` Jairo A. del Rio via ntg-context
2023-04-27 7:52 ` Hans Hagen via ntg-context
2023-04-27 0:50 ` lynx--- via ntg-context
2023-04-27 1:52 ` Aditya Mahajan via ntg-context
2023-04-27 5:11 ` Max Chernoff via ntg-context
2023-04-27 7:58 ` Hans Hagen via ntg-context
2023-04-27 7:38 ` Hans Hagen via ntg-context
2023-04-27 8:32 ` Max Chernoff via ntg-context
2023-04-27 21:51 ` lynx--- via ntg-context
2023-04-27 23:54 ` Max Chernoff via ntg-context
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=462b1f2c-3721-44ae-8aa4-af4010b5c6cd@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).