On 15-05-2015 16:28, Ken Moffat wrote: > On Fri, May 15, 2015 at 08:22:43AM -0300, Fernando de Oliveira wrote: >> On 14-05-2015 15:32, Ken Moffat wrote: >> >>> So, to answer the original question - if evince's configure reports >>> that the DVI backend is enabled, it should be able to display a dvi >>> file - provided that the texlive progs are on the user's PATH (yes, >>> BLFS does that at least for a normal user, but I set my PATH >>> differnetly). But the display will take some time (several seconds >>> for what is a minimal document with only 5 lines of text, so perhaps >>> several minutes for a long real document) because it runs a series of >>> TeX programs, so best to do this from a term in case there are any >>> problems. >>> >>> Also, I don't know _where_ the TeX progs write these logs, and after >>> a succesful run I cannot see them - so debugging any problems might >>> be harder than normal. >> >> Thanks for the research!!! >> >> Yesterday I had a big headache, think it is name migraine, and stopṕed >> working early. So, today I will concentrate in doing as many tickets as >> possible and will postpone this issue. Hope that the small headache I >> still feel will let me work fine today. > > Good luck, but don't put pressure on yourself to get editing done.
Thanks. Could work yesterday. Today, no headache, until now, so it seems to be gone. Hopefully. >> But I do not have libkpathsea anywhere. > > I think that is the difference between binary texlive and the (full, > or overfull if you are a traditionalist ;-) source install. From > source, it goes into /usr/lib. From the binary install, it perhaps > gets statically linked into the programs which reference it. Next time, I will try to build from source. > Kpathsea is intended to be used from within TeX, although we now > know that (at least) evince can use it. >> >> Think I did not install complete TeX, and will do it again perhaps >> tomorrow. And will install libspectre. And will make their use explicit >> in evince's page. > > I've looked at a log of what got installed by install-tl-unx, and > libkpathsea.* is not there, so using the binary will probably not > work. Also, using evince to view even postscript, let alone dvi > files, is not a common requirement - I'm sure most users, even in > BLFS, can get by without them. Understood. >> If necessary, will ask again your help. Thanks, again. -- []s, Fernando -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
