[Pkg-octave-devel] octave2.1_2.1.71-7_i386.changes ACCEPTED
Rafael Laboissiere
rafael at debian.org
Sat Nov 5 09:39:06 UTC 2005
* Christian T. Steigies <cts at debian.org> [2005-11-05 09:29]:
> I am still trying to get a current octave2.1 compiled on m68k.
> I solved the hdf5 problem by manually compiling it, after the file that
> failed to compile would not do me the favour when I tried to debug it. hdf5
> for m68k is in the archive now.
>
> octave2.1 does not build on m68k because of special m68k exceptions for
> ofortran and optimization. The output of dpkg-architecture has changed
> recently:
>
> (unstable)cts at aahz:~>dpkg-architecture -qDEB_HOST_GNU_TYPE
> m68k-linux-gnu
> cts at aahz:~>dpkg-architecture -qDEB_HOST_GNU_TYPE
> m68k-linux
>
> So this change is needed (for m68k, I assume it is the same for arm) to at
> least start a build on m68k. Without it, it fails with:
> checking for Fortran name-mangling scheme... configure: error: cannot compile a simple Fortran program
>
> [...]
Thanks for spotting this problem. I already applied your patch to the SVN
sources.
> I am currently trying to build packages with this fix, [...]
I will wait until it is finished before uploading 2.1.71-8 to unstable.
> [...] will take a while to complete.
The last buildd that worked on m68k (2.1.71-2) took almost three days
to complete:
Finished at 20050707-1035
Build needed 59:55:45, 138080k disk space
Compare with the last ia64 buildd:
Finished at 20051103-1115
Build needed 00:49:56, 205588k disk space
It is two orders of magnitude faster!
--
Rafael
More information about the Pkg-octave-devel
mailing list