Le Tue, Apr 23, 2024 at 07:47:37PM +0200, Frederic Cambus a écrit : > On Tue, Apr 23, 2024 at 03:41:20PM +0200, Landry Breuil wrote: > > > > It's preferring libfmt in /usr/local for headers in some of the compiler > > > commands lines - "-I/usr/local/include -I./.. -I./../fmtlib" - so even > > > if it works now, things will likely break again in the future. > > > > > > It would be best to figure out how to get the -I reordered so that > > > -I./../fmtlib comes before -Iusr/local/include. You can check by > > > installing fmt, editing /usr/local/include/fmt/format.h to add a > > > #error at the top, and make sure that lnav still builds. > > > > and on top of that im not even sure this is worth importing as is, > > because it crashes/segfaults at startup here anyway. > > I previously didn't notice this, it always ran fine here during my tests: > launching it in tmux worked both locally and through SSH. > > But launching it in alacritty outside of tmux indeed results in a crash, > although it works fine in xterm or in a framebuffer console.
interestingly, it started working once i had rm -Rf ~/.lnav. so i guess something something corrupted internal database ? does it work again if you move away ~/.lnav on the machine where it crashes ?
