Bug#344995: [Pkg-octave-devel] Bug#344995: octave-forge: FTBFS (ia64, mips, .../unstable): fixed.h: No such file or directory

2005-12-28 Thread Paul Kienzle
This sounds familiar and may already be fixed in CVS, so hopefully it is just a matter of releasing a new version. I think the hordes of octave-forge developers can manage this before the new year. The steps are as usual: (1) post all outstanding changes to your packages (2) address

Bug#344995: [Pkg-octave-devel] Bug#344995: octave-forge: FTBFS (ia64, mips, .../unstable): fixed.h: No such file or directory

2005-12-28 Thread Rafael Laboissiere
* Steve Langasek [EMAIL PROTECTED] [2005-12-28 02:42]: Package: octave-forge Version: 2005.06.13-4 Severity: serious octave-forge is failing to build on multiple architectures because it's missing an include path while building in the fixed/examples directory: [...] The fixed.h file

Bug#344995: [Pkg-octave-devel] Bug#344995: octave-forge: FTBFS (ia64, mips, .../unstable): fixed.h: No such file or directory

2005-12-28 Thread Joaquim Ortega
This seems to be a regression with the new version of make. In a current sid with the make package from testing (make_3.80-11_i386.deb) octave-forge builts without trouble. Maybe it is related to some of the backward incompatibilities described in the NEWS.Debian.gz of the new version of make, but