Re: building on freeBSD
Bakul Shah <[email protected]> Sat, 23 May 2026 14:36:10 -0700
| Newsgroups | gmane.mail.nmh.devel |
|---|---|
| Message-ID | <[email protected]> |
On May 23, 2026, at 2:04=E2=80=AFPM, Philipp = <[email protected]> wrote: >=20 > [2026-05-23 13:49] Bakul Shah <[email protected]> >>> On May 23, 2026, at 1:33=E2=80=AFPM, Philipp = <[email protected]> wrote: >>>=20 >>> I have some ideas how to fix this: >>>=20 >>> * only output a warning when FreeBSD is detected >>> * fallback to /usr/local/ when the command fails >>> * remove the special handling completly >>> * add a specia --localbase to configure when run on *BSD >>>=20 >>> I have no idea what the best way is to fix this. >>=20 >> What about just creating /usr/port/Mk/* ? >> I just did that (unmounted /usr/port and added the above dir) >> and ./configure completed fine. >=20 > I'm not sure if you want to help me getting nmh build or find a fix = for > the issue. So to be clear: I'm able to workaround this issue. >=20 > Why I have written the mail: I would argue building should either work > without having to tinker on your system or fail with a reasonable = error > message. So I would say this is a bug in the build system. Here's a simpler workaround: BSDPORTMK=3D/dev/null ./configure [But you may have to do a "autoreconf -f" if automake version doesn't match, as was the case on my pi4 freebsd] May be you can help get the build system fixed, given this hint!=