On Sun, Sep 16, 2007 at 07:00:47PM +0200, Kurt Roeckx wrote: > 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 Sounds ok. There is no g77 on armel so technically the [!armel] part is redunant. However f2c exists, so for the fortran77-compiler [!armel] _is_ necessary. > > 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. Right, I forgot libtool is generally copied. -- "rm -rf" only sounds scary if you don't have backups -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
