From: David B. <Dav...@mo...> - 2005-11-04 09:02:15
|
Quentin Spencer wrote: > I tried compiling the cvs version of octave-forge with the cvs version > of octave, and two functions failed to compile: > > 1. main/fixed/fixedNDArray.cc > > fixedNDArray.o > fixedNDArray.cc:407:59: error: macro "MX_ND_REDUCTION" passed 5 > arguments, but takes just 3 > fixedNDArray.cc:421:61: error: macro "MX_ND_REDUCTION" passed 5 > arguments, but takes just 3 > fixedNDArray.cc:436:61: error: macro "MX_ND_REDUCTION" passed 5 > arguments, but takes just 3 > > This appears to be caused by recent changes to octave. I don't know > enough about this code to debug it, but from looking at it, it appears > that this macro has changed periodically in the past and there is > already some cruft in the code to handle different cases. To whoever > fixes this I suggest removing the old stuff since we are trying to > clean up before octave 3.0. Grrr, that ones mine. It seems to me that a new 2.1.x release of octave-forge is a reasonable goal as the code in octave-forge is still compatible with 2.1.x. So I'd like to keep a 2.1.71 (or 2.1.72 if it comes out) and 2.9.4 (when it comes out) compatible version of the this change for now. I'd suggest an octave-forge release soon after the next 2.9 and perhaps 2.1 release. There doesn't seem all that much point to me in completely decrufting octave-forge at this point as when Soren's package management code is include in octave, then the whole paradigm of octave-forge will change and that is the best point to do the decrufting at the time of that transition... Regards David -- David Bateman Dav...@mo... Motorola Labs - Paris +33 1 69 35 48 04 (Ph) Parc Les Algorithmes, Commune de St Aubin +33 1 69 35 77 01 (Fax) 91193 Gif-Sur-Yvette FRANCE The information contained in this communication has been classified as: [x] General Business Information [ ] Motorola Internal Use Only [ ] Motorola Confidential Proprietary |