Re: [OctDev] stripping binaries

[Andy A. <ad...@nc...>]

On Wed, 22 May 2002, Paul Kienzle wrote:
> In the latest release of octave-forge, I moved the binary stripping code
> from sparse/Makefile to octave-forge/Makeconf so now all oct-files are
> stripped after compiling.  This happens to break the Mac OSX version of
> octave-forge, so something has to change.  This is arguably an octave bug,
> so it may be octave which changes.

I also suspect this is an octave bug. The various strip options with
octave don't work well.

1. make install-strip in 2.1.36 doesn't work for me.

2. mkoctfile with the strip options sometimes doesn't work -
   but I forget when.

> Anybody have any opinions on whether oct-files should be stripped?
> I see smaller binaries.  Is that mostly due to the -g option?
> Are there speed considerations, or are those due to -g as well?
> Should we selectively strip some of the binaries?

In my opinion, standard installs of executables should be stripped.
This can be a 10 times saving in space. Developers who can
use gdb know how to leave in symbols anyway.

andy
_______________________________________
Andy Adler,                ad...@nc...