From: Per P. <per...@ma...> - 2003-12-07 22:31:58
|
Hi, I'm forwarding parts of a discussion from help-octave since I think someone might be able to shed some lights on two issues: i) In current CVS, does main/comm check for presence of tex? ii) Could the problem with command history be related to octave-forge in any way? /Per > >>> >>>> The building of the octave-forge routines was not smooth, but >>>> the "make install" seemed to go OK. >>> >>> It would help if you elaborated on "not smooth". >> >> The ./configure gave a long list of NOINSTALLS, but I went ahead >> anyway. >> The "make" file exited complaining >> >> /usr/bin/texi2dvi: tex: command not found >> /usr/bin/texi2dvi: tex exited with bad status, quitting. >> /usr/bin/texi2dvi: see comms.log for errors. >> make[2]: *** [comms.dvi] Error 1 >> rm comms.texi >> make[1]: *** [comm/] Error 2 >> make: *** [main/] Error 2 >> >> I don't have tex (as in LaTex?) on my machine and I thought it was >> related >> only to help file construction, so I went ahead with "sudo make >> install" >> anyway. I could send a copy of the .log file if it would help. > > OK, you've gotten a partial install then, I suppose. This is the > source of your problems. > > Tex is a build-time dependency and doesn't come with the octave binary > install. So, if you want to install octave-forge-2003.06.02 you need > (la)tex. > I seem to recall some discussion about this in the past. If latex is a > dependency, it should be checked for (makeinfo, texi2dvi and texi2html > are present by default but not dvips and dvipdf). > > Your quick'n dirty fix is to remove $(DOCS) from target 'all' in line > 38 of main/comm/Makefile and build/install. > > >>> >>>> >>>> About the time of the octave-forge installation, my history of >>>> commands in >>>> .octave_hist stopped being updated. >>> >>> No idea. What is the value of variables 'history_file' and >>> 'saving_history'? >>> > > [snip] > > Sorry, no idea. I don't think any part of octave-forge messes with the > history stuff. > |