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 outstanding bugs on the bug tracker
(3) address outstanding bugs on the list, or add them to the bug tracker
(4) purge functions which have made it into 2.1.72
(5) test build on windows, os x, linux
Please help out where you can.
Also for all the octave-forge functions you are using, add some test
cases at the end if there are none there already so that we can release
with more confidence.
- Paul
On Dec 28, 2005, at 5:42 AM, Steve Langasek wrote:
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:
[...]
make[4]: Entering directory
/build/buildd/octave-forge-2005.06.13/main/fixed/examples'
Depending ffft.cc
rm -f ffft.d
/usr/bin/g++ -M -I/usr/include/octave-2.1.72
-I/usr/include/octave-2.1.72/octave -O2 -I../ -DHAVE_OCTAVE_21
-DHAVE_RESIZE_AND_FILL ffft.cc | /bin/sed -e
's,^[^:]*/\(.*\.o\):,\1:,' -e 's,ffft\.o,pic/& & ffft.d,g' > ffft.d-t
&& mv ffft.d-t ffft.d
Depending fixed_inc.cc
rm -f fixed_inc.d
/usr/bin/g++ -M -I/usr/include/octave-2.1.72
-I/usr/include/octave-2.1.72/octave -O2 -I../ -DHAVE_OCTAVE_21
-DHAVE_RESIZE_AND_FILL fixed_inc.cc | /bin/sed -e
's,^[^:]*/\(.*\.o\):,\1:,' -e 's,fixed_inc\.o,pic/& & fixed_inc.d,g' >
fixed_inc.d-t && mv fixed_inc.d-t fixed_inc.d
mkoctfile -DHAVE_OCTAVE_21 -v -c ffft.cc
/usr/bin/g++ -c -fPIC -I/usr/include/octave-2.1.72
-I/usr/include/octave-2.1.72/octave -O2 -DHAVE_OCTAVE_21 ffft.cc -o
ffft.o
In file included from ffft.cc:30:
ffft.h:34:19: error: fixed.h: No such file or directory
[...]
A full build log can be found at
<http://buildd.debian.org/fetch.php?pkg=octave-
forge&arch=mips&ver=2005.06.13-4&stamp=1135763004&file=log>.
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.
There are also other errors shown in the build log; I don't understand
why
the build continues on after these other errors, but I assume at least
that
the final error, if not the *only* reason for the build failure, is at
least
*a* reason for the build failure.
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.
Thanks,
--
Steve Langasek Give me a lever long enough and a
Free OS
Debian Developer to set it on, and I can move the
world.
[EMAIL PROTECTED]
http://www.debian.org/
_______________________________________________
Pkg-octave-devel mailing list
[EMAIL PROTECTED]
http://lists.alioth.debian.org/mailman/listinfo/pkg-octave-devel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]