LAM does not recognize gfortran compiler

[Jonathan Eckstein]

Binary package hint: lam4-dev

It appears that the current LAM development package was configured in an environment in which the fortran compiler is called "g77". However, an up-to-date install of the GNU compilers (4.1) yields a system in which the fortran compiler is called "gfortran". Running "mpiff77" results in a message that there is no g77 compiler.

To get the "mpif77" command to work, it thus seems necessary to mix 3.x and 4.1 GNU compilers, or backtrack them all to 3.x. A semi-workaround is to put a symbolic link to gfortran called "g77" somewhere in the execution path. If one does that, then mpif77 is able to compile, but cannot link -- the linker cannot find any mpi routines.

Looking at the LAM website, it appears that the problem could be fixed by configuring and compiling LAM in an environment where gfortran is the only fortran compiler. Perhaps there should be different LAM packages depending on whether the system has the GNU 4.1 or 3.x compilers.

[Cesare Tirabassi (norsetto)]

lam (7.1.2-1.3) unstable; urgency=low

  * Non-maintainer upload.
  * Fix the second argument to main() in the test programs used by configure.
    Fixes FTBFS with gcc-4.3. (Closes: #468065)

lam (7.1.2-1.2) unstable; urgency=low

  * Non-maintainer upload.
  * Upload to unstable

lam (7.1.2-1.1) experimental; urgency=low

  * Non-maintainer upload.
  * transition to gfortran, closes: #456418
  * rename package for long double transition, closes: #430241
  * remove pre-depends on stone-age dpkg version
  * remove versioned depends on essential package findutils and debianutils
  * Depend on ssh-client instead of ssh, closes: #418988
  * Edit changelog to get rid of lintian warning on long changelog