With a fresh compile of octave-2.1.72 (no patches) and
octave-forge from CVS, my debian system doesn't panic.
When I compile and run against the Debian octave 2.1.72-8
it panics on every oct-file in octave-forge. The particular
problem at startup is that dispatch.oct is called by a
number of
On 7 January 2006 at 16:08, Paul Kienzle wrote:
| With a fresh compile of octave-2.1.72 (no patches) and
| octave-forge from CVS, my debian system doesn't panic.
|
| When I compile and run against the Debian octave 2.1.72-8
| it panics on every oct-file in octave-forge. The particular
| problem
On 30 December 2005 at 12:54, Martin Samuelsson wrote:
| Martin Samuelsson @ 2005-12-30 (Friday), 09:23 (+0100)
| I just started rebuilding octave again with DEB_BUILD_OPTIONS set to
| nostrip noopt. Hopefully that will give some clues.
|
| The compilation has finished, but it seems like the
Dirk Eddelbuettel @ 2005-12-30 (Friday), 07:22 (-0600)
| The compilation has finished, but it seems like the build process did
| not honour DEB_BUILD_OPTIONS. (Debian Policy 10.1 [1])
|
[zap]
|
| Unless someone tells me how to easily produce a debugable debian
| package, I'm not spending
reassign 345241 octave-forge
thanks
On Fri, Dec 30, 2005 at 09:06:35PM +0100, Martin Samuelsson wrote:
Dirk Eddelbuettel @ 2005-12-30 (Friday), 07:22 (-0600)
| The compilation has finished, but it seems like the build process did
| not honour DEB_BUILD_OPTIONS. (Debian Policy 10.1 [1])
|
package octave-forge
severity 345241 normal
tags 345241 etch
thanks
* Dirk Eddelbuettel [EMAIL PROTECTED] [2005-12-30 14:23]:
reassign 345241 octave-forge
thanks
[...]
It needs to be reassigned to octave-forge, and this message should do
just that.
Also, since there is no problem with
6 matches
Mail list logo
