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

[Rafael Laboissiere <rafael@debian.org>]

* Steve Langasek <vorlon@debian.org> [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 is in the parent main/fixed directory, not in
> main/fixed/examples; for whatever reason, the build is using the -I../
> argument correctly when recording the dependencies, but then proceeds to
> drop it for the actual build, resulting in the shown errors.

Thanks, Steve, for this detailed bug report.  Several members of the
Debian Octave Group have already stumbled on this problem.  I am fully
puzzled by it and cannot understand why it worked for 2005.06.13-3 and is
failing for 2005.06.13-4.  Something in the chain tool changed and is
playing badly with the upstream Makefile.

I also tried to build the package from the CVS sources, but it failed (at
least) in the same place.  I am afraid this bug has to be fixed by the
upstream authors.

> Because ginac is tied to the KDE ABI transition, and octave-forge
> depends on libginac1.3c2a, it would be appreciated if you could address
> this bug ASAP.

If it only depended on us...

-- 
Rafael