Re: [Pkg-octave-devel] [RFU] octave3.0 to unstable
* Rafael Laboissiere <rafael@debian.org> [2008-02-21 14:15]:
> * Rafael Laboissiere <rafael@debian.org> [2008-02-21 12:02]:
>
> > As an experiment, we could force the build-dependency on arm to be g++-4.3,
> > just to see whether it works better. What do you think ?
>
> Okay, I just make the necessary changes in my last commit. If nobody
> objects, I will commit soon 3.0.0-4 (as in SVN r1205) to unstable.
The arm build daemon tried to build the package yesterday [1]. It failed
with:
g++ -c -fPIC -I. -I.. -I../liboctave -I../src -I../libcruft/misc
-DHAVE_CONFIG_H -Wall -W -Wshadow -Wold-style-cast -O0 -g0 Array-i.cc -o
pic/Array-i.o
Assembler messages:
Fatal error: can't create pic/Array-i.o: No such file or directory
make[3]: *** [pic/Array-i.o] Error 1
make[3]: Leaving directory `/build/buildd/octave3.0-3.0.0/liboctave'
make[2]: *** [liboctave] Error 2
make[2]: Leaving directory `/build/buildd/octave3.0-3.0.0'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/build/buildd/octave3.0-3.0.0'
make: *** [make-arch-stamp] Error 2
dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binary-arch gave
error exit status 2
I hope that this is not a problem releated to g++ 4.3 but a random failure
in the autobuilder system. Let us see how it goes for 3.0.0-5 on arm.
[1] http://buildd.debian.org/fetch.cgi?&pkg=octave3.0&ver=1%3A3.0.0-4&arch=arm&stamp=1203772565&file=log
--
Rafael
Reply to: