From: Eric Wong <e@80x24.org>
To: "Hipólita Yarona" <hipyarona@gmail.com>
Cc: meta@public-inbox.org
Subject: Re: install procedure apparently broken on FreeBSD 14.1-RELEASE-p5
Date: Tue, 26 Nov 2024 18:02:19 +0000 [thread overview]
Message-ID: <20241126180219.M464633@dcvr> (raw)
In-Reply-To: <CAPyh5WR1DA0ZZW86Pq6Vpb+D2KiRgqs6LG71-an-63uqr1XJ_g@mail.gmail.com>
Hipólita Yarona <hipyarona@gmail.com> wrote:
> $ uname -a
> FreeBSD my.host 14.1-RELEASE-p5 FreeBSD 14.1-RELEASE-p5 GENERIC amd64
> W: gmake is currently required to build manpages
Which version of public-inbox are you using?
73fe3421f1ecbdc8 (build: support doc generation w/o GNU make,
2019-12-01) removed the gmake requirement for manpages and that
was in v1.3.0 (2020-02-10)
Latest release is v1.9.0 but unfortunately still ancient (2022).
I recommend latest from https://80x24.org/public-inbox.git since
it has more *BSD compatibility improvements for existing
features, but I'm stuck trying to implement new features that I
can't wrap my head around :<
That said, I do test nearly everything on FreeBSD before pushing
but I've never tried `make install' (I normally do `make
symlink-install' to save inodes)
> t/altid_v2.t ............... skipped: DBD::SQLite missing for altid_v2.t
FWIW, I strongly recommend DBD::SQLite, just about everything
since 2015 relies on it (threading view, NNTP).
next prev parent reply other threads:[~2024-11-26 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 16:49 install procedure apparently broken on FreeBSD 14.1-RELEASE-p5 Hipólita Yarona
2024-11-26 18:02 ` Eric Wong [this message]
2024-11-26 23:58 ` Hipólita Yarona
2024-11-27 0:05 ` Hipólita Yarona
2024-11-27 0:30 ` Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241126180219.M464633@dcvr \
--to=e@80x24.org \
--cc=hipyarona@gmail.com \
--cc=meta@public-inbox.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).