Re: [OctDev] Problems with comm docs and history on OS X

[Per P. <per...@ma...>]

I'll split my reply in two.

On Monday, December 8, 2003, at 11:08 AM, Paul Kienzle wrote:

>
> On Dec 7, 2003, at 5:31 PM, Per Persson wrote:
>
>> 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?
>
> main/comm doesn't use tex, it uses texi2dvi.  My guess is that the 
> DarwinPorts
> texi2dvi is not installing the appropriate prerequisites.

This problem is unrelated to DarwinPorts, the binary was obtained 
elsewhere. Nevertheless, the problem remains that the texi2dvi (that 
comes with Apples dev tools) gives this error:

/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

Now, it seems that the installed texi2dvi is pretty old so it may be a 
version problem:
[per ~] % texi2dvi -v
texi2dvi (GNU Texinfo 4.2) 1.1.1.1


> Should we be responsible
> for that in octave-forge?  I don't think so, given that we are already 
> checking that
> the command texi2dvi exists.

No, certainly not. But if it is a version problem, then that must be 
checked for IMHO.


>
>> ii) Could the problem with command history be related to octave-forge 
>> in any way?
>
> Not that I know of.

That was my conclusion as well.

/Per