On 11/06/08 11:53 +0200, Michael Creel wrote:
> On Wed, Jun 11, 2008 at 11:38 AM, Thomas Weber <email@example.com
> > Am Mittwoch, den 11.06.2008, 10:57 +0200 schrieb Michael Creel:
> I was getting stripped .oct files quite recently. PelicanHPC v1.5.1 is basedYour Makefile is a mess :),
> on Lenny (made using live-helper), and it has Octave v3.0.1. It was released
> 20 May, using whatever was in Lenny at the time. I have already tried the
> changes in your mpitb.diff, and I still get large oct files. I don't think
> that the Makefile actually uses mkoctfile to compile, it uses it only to
> read configurations (maybe I'm wrong about that). Thus, this change has no
> effect on the .oct files that are produced.
just like our debian/rules file for Octave. Anyway, it seems you are using
several flags from mkoctfile, maybe one of them had the strip part in it?
There hasn't been any change upstream. The default as shipped in Octave by
> When you say that this is an upstream isssue, do you know exactly what
> change has been made?
octave.org is to not strip .oct files. The reason for that kind of policy
(almost every project does it like that): it's simple to strip the files if
needed and helpful if the debug symbols are there to start with.
If you want to strip the files, something like the 'find' command I sent
earlier should be fine. Just run it as part of the all: command or whatever
the default is.
I don't really see a problem here, having files not stripped is a sensible