[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: Paul Kienzle
Subject: Re: making octave-forge on OS X -- "forced strip"?
Date: Fri, 14 Mar 2003 17:46:55 -0500
User-agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.3a) Gecko/20021212

Per Persson wrote:

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

I redid the build system a bit so that
octave-forge asks octave for the
canonical_host_type it was configured
for, and based on that it decides whether
to strip and which directories to install.
Any instructions you have regarding
NOINSTALL in extra/MacOSX are
no longer relevant.

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?)

The CVS version of octave-forge extends support
back to octave 2.1.36.  The last release tarball requires
2.1.43 if I recall correctly.  Is this worth a point release?

Paul Kienzle

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]