[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: building from CVS
From: |
John W. Eaton |
Subject: |
Re: building from CVS |
Date: |
Thu, 25 May 2000 20:53:02 -0500 (CDT) |
On 25-May-2000, Shaun Cloherty <address@hidden> wrote:
| Ben Sapp wrote:
|
| > I can compile from the CVS archive on IRIX with the following commands:
| >
| > << snip >>
| >
| > I tried for the first time to do this on a Linux machine. It will
| > compile every thing with the exception of lex.cc.
|
| I had the same problem building from the CVS archive, issuing 'make lex.cc'
| separately appeared to succeed, but on further investigation I noticed a
| rather obscure warning relating to gperf, which wasn't installed. I
| installed gperf and all was well...... almost.
|
| I still cannot get the 'info' files to build correctly, it seems
| 'octave.texi' in the doc/interpreter subdir doesn't exist..... even after a
| 'cvs update'. Any ideas on how to overcome this would be greatly
| appreciated.
Hmm. It is there in the anoncvs directory. However, there was a
point in time when it was missing. Is is possible that you used some
option for cvs that set sticky tags or dates? What happens if you use
cvs update -A?
BTW, it is probably better to report problems with the 2.1.x sources
to the octave-maintainers mailing list.
Thanks,
jwe
-----------------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.
Octave's home on the web: http://www.che.wisc.edu/octave/octave.html
How to fund new projects: http://www.che.wisc.edu/octave/funding.html
Subscription information: http://www.che.wisc.edu/octave/archive.html
-----------------------------------------------------------------------