From: Eric Wong <e@80x24.org>
To: Filipe Manana <fdmanana@kernel.org>
Cc: meta@public-inbox.org
Subject: Re: Trouble running lei
Date: Tue, 3 May 2022 11:37:09 +0000 [thread overview]
Message-ID: <20220503113709.GA6803@dcvr> (raw)
In-Reply-To: <CAL3q7H4xFF3bmq1=08Yq6Bz5iMQ9Kzru6Y3mkh+m3o1CCNBsWQ@mail.gmail.com>
Filipe Manana <fdmanana@kernel.org> wrote:
> Hello,
>
> I tried both 'master' branch and tag v1.8.0, I did the documented build steps:
>
> $ git clone https://public-inbox.org/public-inbox.git/
> $ cd public-inbox
>
> $ perl Makefile.PL
> $ make
> $ echo $? # success, prints 0
>
> $ cd certs
> $ /usr/bin/perl ./create-certs.perl
> $ cd ..
> $ make test
> (...)
Any messages about missing dependencies when running tests?
(e.g. Xapian)
Inline::C or Socket::Msghdr shouldn't be required with 1.8
on most arches...
> All tests successful.
> Files=157, Tests=6785, 491 wallclock secs ( 0.77 usr 0.13 sys + 39.65
> cusr 14.90 csys = 55.45 CPU)
Fwiw, "make check" or "make check-run" can be a lot faster on SMP.
> Result: PASS
>
> $ make symlink-install
>
> $HOME/bin is included in my $PATH, but when I run 'lei', I get an error:
>
> $ lei q -o ~/Mail/overlay -I https://lore.kernel.org/all -t
> 'dfn:fs/btrfs/* AND rt:3.month.ago..'
> Attempt to reload PublicInbox/LeiXSearch.pm aborted.
Odd, "Attempt to reload %s aborted" coming from perl itself means it
already tried and failed before. (man perldiag)
Were there previous errors from other commands?
Perhaps it's already running lei-daemon as an older version?
"lei daemon-kill" should kill it and it'll restart on the next
command, unless something else got wedged.
I've been meaning to make the daemon stuff "worth it"
w.r.t. automatic updates/flag/keyword sync (inotify/IDLE) but
haven't gotten around to it, yet :x
> Compilation failed in require at
> /home/fdmanana/git/hub/public-inbox/lib/PublicInbox/LeiQuery.pm line
> 74.
>
> This is on a Ubuntu 20.04.3 LTS distro.
> I have it working on a Debian SID box without any problems (it was set
> up several months ago).
>
> Any ideas about what's wrong?
Probably daemon-kill will get rid of an old version that's
already running (and verifying that it's actually dead).
next prev parent reply other threads:[~2022-05-03 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 11:15 Trouble running lei Filipe Manana
2022-05-03 11:37 ` Eric Wong [this message]
2022-05-03 12:50 ` Filipe Manana
2022-05-03 15:24 ` Konstantin Ryabitsev
2022-05-03 20:32 ` 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=20220503113709.GA6803@dcvr \
--to=e@80x24.org \
--cc=fdmanana@kernel.org \
--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).