[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: making octave-forge on OS X -- "forced strip"?

From: John O'Leary
Subject: Re: making octave-forge on OS X -- "forced strip"?
Date: Fri, 14 Mar 2003 17:39:33 -0600

I was building from the 2003.02.22 tarball. I switched to the latest CVS and the builds are progressing much further now.

The current error is this:

texindex: ./comms.cp: not a texinfo index file
/sw/bin/texi2dvi: line 602: 25154 Segmentation fault $texindex $index_files 2>&5 1>&2
/sw/bin/texi2dvi: texindex exited with bad status, quitting.
make[1]: *** [comms.dvi] Error 1
rm comms.texi

I assume this means there's just some tex component that I haven't installed. (2 week old machine so lots of stuff is missing) All the oct files are compiling just fine, so my build issues now appear to be unrelated to octave. I'll go back and RTFM and finish off my installs tomorrow when I have more time. (sadly, installing octave has been a way for me to procrastinate)

A further tiny bug in INSTALL.MacOSX:

You say "Change the options to cp in to read:" at the step before you say to run ./configure. Since configure generates from (at least AFAIK), shouldn't the instruction be to "Change the options to cp in ** to read:"?

One more question that is perhaps off-topic for this forum: Is anyone working on an octave equivalent for Matlab's pmtm command? It's the only one I'll be missing after I get octave-forge installed. I'd write it myself but I am not confident enough in my understanding of multitaper spectral analysis to implement it yet. (I know, implementation would be a good way to learn)

Thanks again for all the help,

On Friday, March 14, 2003, at 03:43  PM, Per Persson wrote:

On Friday, March 14, 2003, at 10:05 PM, John O'Leary wrote:

        I found the INSTALL.MacOSX file that came with octave-forge quite


except for one line:

"Comment out forced strip command in extra/mex/Makefile"

Could someone tell me what a "forced strip command" is?  I've read
through that Makefile and I can't find any line that I could imagine
someone would call "forced strip."

Apparently that "forced strip" went away between version 1.4 and 1.5 some three months ago, docs need an update.
CVS diff if you're interested: extra/mex/Makefile.diff?r1=1.4&r2=1.5

("Forced" refers to the makefile overriding mkoctfile behaviour)

 Anyway, I built octave-2.1.40-1
using fink built from CVS sometime in the past couple days, and I
followed all the instructions in INSTALL.MacOSX for building
octave-forge except for the above-mentioned "forced strip" line. After
a sane-looking run of the configure script, my attempts to make
octave-forge fail with the following messages:

g++ -c -no-cpp-precomp -I/sw/include -I/sw/include/octave-2.1.40
-I/sw/include/octave-2.1.40/octave -I/sw/include -g -O2 -Wall
-DHAVE_OCTAVE_21 -o mex.o In function `octave_value_list call_mex(callstyle, const
    octave_value_list&, int)': parse error before `*' token parse error before `*' token `argin' undeclared (first use this function) (Each undeclared identifier is reported only once for each
    it appears in.) `argout' undeclared (first use this function)
make[2]: *** [mex.o] Error 1
make[1]: *** [mex/] Error 2
make: *** [extra/] Error 2
Does the above sound like something that would be fixed if I commented
out the forced strip line, or am I doing something else wrong?

Compiles OK here, updated from CVS about 5 min ago.
(Did you use CVS or tarball? What version of tarball in that case?)

searches on "forced strip", naturally, returned a list of porn sites.


Per Persson
Blekinge Institute of Technology
Dept. of Signal Processing and Telecommunications

e-mail: address@hidden

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

Octave's home on the web:
How to fund new projects:
Subscription information:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]