9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] kerTeX: LaTeX recipe fix for Plan9
Date: Sun, 30 Oct 2022 16:41:21 -0700	[thread overview]
Message-ID: <CAJSxfmJthSsHAE8TjtK2BKmCxHkY3fc+dLZMNM_oMfFhKx8ewQ@mail.gmail.com> (raw)
In-Reply-To: <Y0goxo08S2fkRN94@polynum.com>

[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]

I just did a full install of the stable version in my local evolutionary
branch of 9legacy using the get_mk_install.rc script.
I had to extend XCPPFLAGS in "kertex_T/lib1/web/Makefile.ker" to include
"-D_SUSV2_SOURCE"

Also, I can't find latex.sh in the installed packages. Did I miss a step?

On Thu, Oct 13, 2022 at 8:05 AM <tlaronde@polynum.com> wrote:

> The latest version of the recipe used utilities in a way not matching
> Plan9 (rmdir(1) or mv(1) for directories...) and the use of the mf(1)
> binary was made without ensuring the kerTeX directory was in the path.
> 
> This is corrected in the new recipe latex.sh (tested on 9front).
> --
> Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
>              http://www.kergis.com/
>             http://kertex.kergis.com/
> Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T5c7149f289645c43-M37db84320f46af5cb7639c2a
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 2723 bytes --]

  reply	other threads:[~2022-10-30 23:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13 15:03 tlaronde
2022-10-30 23:41 ` Skip Tavakkolian [this message]
2022-10-31  8:27   ` tlaronde
2022-10-31 11:04     ` tlaronde
2022-11-01 21:12     ` Skip Tavakkolian
2022-11-02 11:59       ` tlaronde

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=CAJSxfmJthSsHAE8TjtK2BKmCxHkY3fc+dLZMNM_oMfFhKx8ewQ@mail.gmail.com \
    --to=skip.tavakkolian@gmail.com \
    --cc=9fans@9fans.net \
    /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).