On Tue, May 3, 2022 at 12:37 PM Eric Wong <e...@80x24.org> wrote: > > Filipe Manana <fdman...@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.
Oh, I didn't know about it. Good to know. > > > 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. Ah, running "lei daemon-kill" fixed it. I don't know if I did something wrong before, but after running that, lei is now working fine. Thanks! > > 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).
