From: Eric Wong <e@80x24.org>
To: "Štěpán Němec" <stepnem@smrk.net>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] doc: INSTALL: note OpenBSD xapian-bindings-perl package
Date: Fri, 25 Aug 2023 20:43:18 +0000 [thread overview]
Message-ID: <20230825204318.M672207@dcvr> (raw)
In-Reply-To: <20230825171916+0200.946103-stepnem@smrk.net>
Štěpán Němec <stepnem@smrk.net> wrote:
> On Thu, 24 Aug 2023 21:51:03 +0000
> Eric Wong wrote:
> > Štěpán Němec <stepnem@smrk.net> wrote:
> >> Tangentially related: I've taken this opportunity to review my (OpenBSD)
> >> install script and found one other package I needed to install that
> >> isn't mentioned in INSTALL, namely, p5-IO-Socket-SSL.
> >
> > Is there a test which fails without it? It should be optional
> > (warnings emitted, functionality degrading gracefully and tests
> > automatically skipped).
>
> Yeah, false alarm, sorry. I now tried a clean install, and it (what I
> want, i.e., NNTP and HTTP) does work without it. I guess I only needed
> it because I initially tested public-inbox handling TLS itself? I later
> thought better of it anyway and put it behind a proxy.
Yeah, though I'm not comfortable recommending the popular open core
reverse proxy so I intend to implement one in Perl5 at some point...
(I currently use a GPL-3+ Ruby reverse proxy, but Ruby introduces
new incompatibilities every year so I'm moving away from it).
> t/cindex.t ................... 37/?
>
> Has been stuck there for a Real Long Time now (half an hour or so).
>
> (That's "make test" with latest master.)
>
> Both the HTTP and NNTP servers do work, though, so I guess it's
> something with the test or the cindex functionality (which I know next
> to nothing about).
-cindex is a new feature and still under development and the
good news is I'm able to reproduce it. I will try to fix it soon.
> All info I have for you is a stuck perl process after ^Cing out of the
> test run:
>
> USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
> pi 18600 0.0 6.5 53884 66800 p1 I 3:51PM 0:04.99 perl: -cindex -q --prune -d /tmp/pi-cindex-18600-9QG_/ext (perl)
>
> Attaching to the process didn't provide anything (nothing from ktrace,
> continuing after attaching with gdb got stuck, too, killing the gdb
> process finally got rid of the perl one as well).
Yeah, ktrace doesn't seem to tell the actual syscall it's stuck on
(IIRC I had the same experience on FreeBSD)
> > On a side note, running OpenBSD i386 via QEMU on amd64 Linux is
> > very slow. Hoping OpenBSD amd64 will be faster...
>
> My experience with QEMU is limited, but running amd64 OpenBSD on an
> amd64 Linux host seemed OK last time I tried (2 years ago?). Running
> aarch64 Linux on amd64 Linux was unusably slow, even on a recentish
> laptop.
Yeah, I just setup OpenBSD amd64 on a amd64 Linux host and it seems fine.
I'll try to do more work on it (as I do in FreeBSD) to iron out
portability problems.
<snip> Thanks for the VPS note though I avoid doing anything which
has even slightest possibility of being interpreted as a commercial
endorsement (even if it's "free as in beer").
next prev parent reply other threads:[~2023-08-25 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 19:35 [PATCH] doc: INSTALL: note OpenBSD xapian-bindings-perl package Eric Wong
2023-08-24 20:30 ` Štěpán Němec
2023-08-24 21:51 ` Eric Wong
2023-08-25 15:19 ` Štěpán Němec
2023-08-25 20:43 ` Eric Wong [this message]
2023-08-26 6:03 ` 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=20230825204318.M672207@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=stepnem@smrk.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 read-only IMAP folder(s) and NNTP newsgroup(s).