Re: octave forge

[Robert Leach]

Okie dokie.  When I tried the make -k, I got a TON of this (thousands 
of lines!).  Here's the end of it.  It's still going as I type and is 
behaving better now after its rant...


Overfull \hbox (2955.31927pt too wide) in paragraph at lines 
23403--23406
 @textrm i-|

Overfull \hbox (2970.2539pt too wide) in paragraph at lines 23403--23406
 @textrm nary|

Overfull \hbox (2973.05223pt too wide) in paragraph at lines 
23403--23406
 @textrm parts |
[1587]
Overfull \hbox (2964.44429pt too wide) in paragraph at lines 
23407--23408
 address@hidden See|

Overfull \hbox (2969.98013pt too wide) in paragraph at lines 
23407--23408
 @textrm also:|

Overfull \hbox (3004.32059pt too wide) in paragraph at lines 
23407--23408
 @textrm randn,awgn |
[1588] )
(@end occurred inside a group at level 116)
(see the transcript file for additional information)
Output written on comms.dvi (1591 pages, 1885928 bytes).
Transcript written on comms.log.
/usr/lanl/bin/texi2dvi: tex exited with bad status, quitting.
/usr/lanl/bin/texi2dvi: see comms.log for errors.
make[3]: *** [comms.dvi] Error 1
make[3]: Target `all' not remade because of errors.
rm comms.texi
make[3]: Leaving directory 
`/home/local/octave-forge-2004.02.12/main/comm/doc'
make[2]: *** [doc] Error 2
make[2]: Target `all' not remade because of errors.
make[2]: Leaving directory 
`/home/local/octave-forge-2004.02.12/main/comm'
make[1]: *** [comm/] Error 2
make[2]: Entering directory 
`/home/local/octave-forge-2004.02.12/main/general'
mkoctfile -DHAVE_OCTAVE_21 -v bitand.cc
g++ -c -fPIC -I/usr/local/include/octave-2.1.55 
-I/usr/local/include/octave-2.1.55/octave -I/usr/local/include -g -O2 
-DHAVE_OCTAVE_21 bitand.cc -o bitand.o
cc1plus: warning: changing search order for system directory 
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system 
directory


I'll let you know if I run into another problem.

Rob

On Tuesday, March 2, 2004, at 08:29  PM, Paul Kienzle wrote:

> I have no idea what is going on with the comms docs.
>
> The simplist thing for you to do is
>
>         make -k
>
> so that errors are ignored.  Some things may not compile,
> but the routines in octave-forge are mostly independent,
> so that won't be so bad.
>
> Paul Kienzle
> address@hidden
>
> On Mar 2, 2004, at 8:22 PM, Robert Leach wrote:
>
> > OK,
> >
> > Well, I took the suggestion below (to use 2.1.55) and after a timely 
> > false start, I ran into a new problem with installing octave-forge:
>
>
>
> -------------------------------------------------------------
> Octave is freely available under the terms of the GNU GPL.
>
> Octave's home on the web:  http://www.octave.org
> How to fund new projects:  http://www.octave.org/funding.html
> Subscription information:  http://www.octave.org/archive.html
> -------------------------------------------------------------
=====================================================================
= Robert W. Leach                                                   =
= Los Alamos National Lab                                           =
= Bioscience Division: Bioinformatics & Computational Biology Group =
= MS M888                                                           =
= Los Alamos, NM 87545                                              =
= address@hidden                                                 =
= Work: 505-667-2307                                                =
= Cell: 505-310-3759                                                =
=====================================================================
Work Calendar & To-Do 
List:	http://66.93.220.101/phpicalendar/week.php?cal=Work



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------