From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Alan BRASLAU <alan.braslau@comcast.net>
Subject: Re: OpenBSD install broken
Date: Sat, 21 Sep 2019 13:22:31 +0200 [thread overview]
Message-ID: <CALBOmsZxFtY9w2cE6pUZ+Tbjh4iJGdvTYOrcksgfLOZR6vL7jQ@mail.gmail.com> (raw)
In-Reply-To: <327ab547-be27-47c3-b2fb-796ca42a2d13@me.com>
Dear Robert,
On Sat, 21 Sep 2019 at 01:09, Robert Krug wrote:
>
> Now, to the reason for this note. I recently tries to install context on an OpenBSD 6.5 AMD64
> system, but the install failed. Thanks to some helpful emails in the archives from 2017 and 2018,
> I was able to get this working by editing mtxrun and mtx-update.sh.
This would be really nice to fix eventually.
Hans, we do have all the required files:
https://distribution.contextgarden.net/setup/openbsd6.5/
https://distribution.contextgarden.net/setup/openbsd6.5-amd64/
...
https://distribution.contextgarden.net/current/bin/luatex/openbsd6.5-amd64/
...
but the problem is that mtxrun knows the platform under the name of
"openbsd-amd64" rather than "openbsd6.5-amd64".
The first-setup.sh script already correctly recognizes the name by
doing the following:
system=`uname -s`
case "$system" in
OpenBSD)
version=`uname -r`
platform="openbsd${version}-amd64" ;; # for 64-bit one; a
separate call for 32-bit of course
while mtxrun "ignores" the version name, but also ignores the
parameter being passed as
mtxrun --script bin/mtx-update.lua --platform=openbsd6.5-amd64
> I include what I did below.
Thanks.
> 1) Do the usual:
>
> mkdir context && cd context
> rsync -ptv rsync://contextgarden.net/standalone/setup/first-setup.sh .
> ./first-setup.sh
>
> This will silently fail, because
> bin/mtx-update.lua
> bin/mtxrun
> do not recognize openbsd.
>
> 2) Edit bin/mtxrun:
>
> We need to define a "good" version of resolvers.platform(t,k)
> At line 4049, there is a default definition. Replace it with:
>
> function resolvers.platform(t,k)
> local platform="openbsd6.5-amd64"
> os.setenv("MTX_PLATFORM",platform)
> os.platform=platform
> return platform
> end
It would be ideal to fix this properly instead, for everyone else.
This is a good recipe for a workaround, but we need something better.
In my opinion this might be best to maybe even fix inside luatex
sources themselves.
> 6) Finally, the setuptex script gives me an error message:
>
> megaera$ . /home/<name>/Context/tex/setuptex
> /bin/ksh: /home/<name>/Context/tex/setuptex[163]: ${.sh.file}": bad substitution
>
> but it is not hard to set the path correctly:
>
> PATH=$PATH\:/home/<name>/Context/tex/texmf-openbsd6.5-amd64/bin ; export PATH
This is something that I need to fix independently in the installation
script. Do you have any clue what could be done to make it work
properly on OpenBSD?
Mojca
PS: Hans, for some reason the 32-bit virtual machine for OpenBSD 6.5
seems broken in a bad way (I doesn't even reach the login screen), no
clue what's wrong, and I don't have extensive experience with OpenBSD
either. I could keep investigating, but I'll probably simply end up
setting up a fresh one. It would be helpful to maybe do some disk
health checks on the server, just in case.
___________________________________________________________________________________
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:[~2019-09-21 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 23:02 Robert Krug
2019-09-21 11:22 ` Mojca Miklavec [this message]
2019-09-23 20:38 Robert Krug
2019-10-08 17:24 Damien Thiriet
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=CALBOmsZxFtY9w2cE6pUZ+Tbjh4iJGdvTYOrcksgfLOZR6vL7jQ@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--cc=alan.braslau@comcast.net \
--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).