Le 20/11/2019 à 01:03, Ken Moffat via blfs-support a écrit : > On Tue, Nov 19, 2019 at 08:23:42PM +0100, Christopher Gregory via > blfs-support wrote: >> >>> Sent: Tuesday, November 19, 2019 at 5:40 AM >>> From: "Armin K. via blfs-support" <[email protected]> > [...] >>> Hi, >>> >>> Thing is, it appears that it finds libkpathsea in /opt/texlive/2019/lib >>> (LIBRARY_PATH, LD_LIBRARY_PATH), but not includes in >>> /opt/texlive/2019/include. In your output, you have kpathsea/debug.h in >>> /opt/texlive/2019/include, but that path is not in your compiler include >>> path (C_INCLUDE_PATH, CPLUS_INCLUDE_PATH). >>> >>> From the look at texlive setup instructions, it doesn't append the >>> include path in any way, so you probably need to do it yourself via, for >>> example, CFLAGS='$CFLAGS -I/opt/texlive/2019/include' (same for >>> CXXFLAGS) when compiling evince ... >>> >>> The real problem is not that it finds texlive or not, it's that it finds >>> part of it (library, but not headers). Try renaming your texlive dir, it >>> shouldn't need --disable-dvi then. > [...] >> >> Hello Armin, >> >> Adding that line to the configure line fixed it. I had to use " instead of >> ' in the confiure line, otherwise it complained that gcc could not create >> executables and failed. This really does need to be added to the book. >> >> Thanks for this solution. >> >> Regards, >> >> Christopher. > > I think I've fixed this in r22384 (tested on a recent system where > texlive has been installed, and on another where it has not). > Thanks to you both for the report and the diagnosis. > > I would not normally see this problem because I install evince > before texlive, and then I do not usually update evince on my > short-lived systems. > > (I say "I think" because it was just DESTDIR installs and I have no > use for the DVI backend). > > System TeX is nothing but trouble ;-) For a different example, see > the thread at > https://tug.org/pipermail/tex-live/2019-November/044330.html - > perhaps we should only ever install it in /home, for a single > user. >
Well I think the main problem in this thread is that the OP has two installations of texlive, one in system, and one in $HOME, and that both installations are somehow entangled because root's $TEX_SOMETHING_PATH includes user's $HOME... I think evince is wrong in guessing include paths just from finding a library (or an executable, not sure)... Pierre Still overwhelmed with the steep learning curve for using glib2 and daemons for blocaled... -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
