9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: skip.tavakkolian@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] Git client
Date: Mon, 31 Aug 2020 21:51:21 -0700	[thread overview]
Message-ID: <B7F3462303CEF992C658ED6E612BAFF5@eigenstate.org> (raw)
In-Reply-To: <CAJSxfmLwDxS1qpSjMT1v40z5hURLyhCn_KhUpyGqCdZY3khDAg@mail.gmail.com>

> Are there any build instructions?  ape/make can't seem to handle the
> Makefile (sources from git repo)


Looking at the changes in git, it seems like
lufia expected it to be built with gmake. I'm
not sure which port lufia used, but there's one
sitting in mveety's ports repo, here:

https://code.9front.org/hg/ports/file/82187053e44b/dev-utils/gmake

(you need both the patches and the tarball; I think that
the ports repo is likely to work on 9legacy, but I don't
know if anyone's tested it.)

When I tried building it, I also realized I needed perl
for the libressl build. That's been updated recently as
well (https://github.com/Perl/perl5/pull/17891), but you
may need some cpp changes that I made to get it to work.

The version of cpp shipped with 9legacy, I think, gets
operator associativity wrong: it computes '1 - 1 + 2'
as '1 - (1 + 2)' instead of '(1 - 1) + 2', which breaks
some '#if' statements, if I recall correctly.


  reply	other threads:[~2020-09-01  4:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-21 11:05 Kyohei Kadota
2019-04-22 12:09 ` Dave MacFarlane
2019-04-22 12:44   ` hiro
2019-04-22 13:49     ` Kyohei Kadota
2019-04-22 14:18       ` hiro
2019-04-22 12:58   ` Kyohei Kadota
2019-04-22 13:34     ` Dave MacFarlane
2020-08-31 18:27 ` Skip Tavakkolian
2020-09-01  4:51   ` ori [this message]
2020-09-01  9:20   ` Kyohei Kadota
2019-04-22  2:40 ori
2019-04-22  4:39 ` Jens Staal
2019-04-22 10:19   ` Lucio De Re
2019-04-22 12:49     ` Jens Staal

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=B7F3462303CEF992C658ED6E612BAFF5@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9fans@9fans.net \
    --cc=skip.tavakkolian@gmail.com \
    /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).