On Sun, Sep 16, 2007 at 05:35:23PM +0300, Riku Voipio wrote: > Actually, since thursday we have had perfectly[1] functioning java for armel. > Java on old arm port is unlikely to ever reach fully functional state, > as the upstream has little interest on it. > > g77 remains unavailable for armel, instead we intend to migrate > the whole of Debian to gfortran[2] (last g77 was included with gcc 3.4..). > So one option is to change the fortran dependency to: > > g77 | gfortran [armel] | fortran77-compiler > > Eventually it should just come down to: > > gfortran | fortran77-compiler
The version in experimental already uses gfortran | fortran95-compiler. The version from unstable also checks things like f95, so I should probably also include that in unstable. So, how about: g77 [!armel] | fortran77-compiler [!armel], gfortran | fortran95-compiler > but without testing of what happens if you use gfortran-compiled > libtool and apps still using g77, I guess it might be a bit too early > for that. I don't think you can use gfortran if the applications wants to use g77. Anyway, this only affects the /usr/bin/libtool that is shipped. Most applications have their own copy of libtool and should have the needed build-dependencies themself. kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
