From: Robert Krug <destiny6@mac.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: OpenBSD install broken
Date: Mon, 23 Sep 2019 20:38:23 -0000 [thread overview]
Message-ID: <cbb43d57-640e-478d-824d-726ba26f03ac@me.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1530 bytes --]
On September 21, 2019 at 4:22 AM, Mojca Miklavec <mojca.miklavec.lists@gmail.com> wrote:
On Sat, 21 Sep 2019 at 01:09, Robert Krug wrote:
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
Shell scripting has always been a mystery to me. For what it is worth,
however, here is what I was able to come up with:
megaera$ cat test
echo "$SHELL"
echo "$KSH_VERSION"
SCRIPTPATH="$_"
OWNPATH=$(cd -P -- "$(dirname -- "$SCRIPTPATH")" && pwd -P)
echo $OWNPATH
megaera$ ./test
/bin/ksh
@(#)PD KSH v5.2.14 99/07/13.2
/home/<name>/Temp
It seems that OpenBSD uses public domain ksh also known as ksh88, as
opposed to the more common ksh93. I also found on the internet the
following code snippet for testing ksh versions:
case "$KSH_VERSION" in
(*MIRBSD*|*PD*|*LEGACY*) printf '%s\n' "$KSH_VERSION" ;;
(*) [ -z "$ERRNO" ] && printf '%s\n' "${.sh.version}" || echo ksh88/86 ;;
esac
All that said however, while it would be nice to have setuptex work on
OpenBSD also, I think anyone using it can set their own paths if they
have to.
Robert
[-- Attachment #1.2.1: Type: text/html, Size: 2475 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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 reply other threads:[~2019-09-23 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 20:38 Robert Krug [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-08 17:24 Damien Thiriet
2019-09-20 23:02 Robert Krug
2019-09-21 11:22 ` Mojca Miklavec
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=cbb43d57-640e-478d-824d-726ba26f03ac@me.com \
--to=destiny6@mac.com \
--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).