Date: Wed, 3 Oct 2007 09:48:30 +0200 From: "Harald Servat" <redcrash@gmail.com> To: freebsd-ports@freebsd.org Subject: papi port, fortran issues Message-ID: <d825e0270710030048s3a1633fco9d4d096843aaf5b2@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hello to everybody,
recently I received an automated mail about a port I'm maintaining. Such
mail includes a full report (which is good in order to review the problems
;) ) of the port build on amd64/freebsd7.
The program needs fortran compiler, and looking at the report, I see that
fortran compiler is installed, however the compiler name is gfortran42 (due
to the gcc package is 4.2 I think). As the configure of the ported program
does not look for gfortran42 explicitly (but looks for gfortran, g77,
fortran, xlf and so) it fails when trying to compile the fortran code.
So two questions arise to my mind,
and which is the good way to solve this? Maybe should I look for
gfortran42 (and change it for every compiler version), or should gcc package
install a softlink from gfortran to gfortran42 --or the latest installed
version--?
why this doesn't happen on i386/freebsd7?
Regards,
--
_________________________________________________________________
Empty your memory,
with a free()...
like a pointer!
If you cast a pointer to an integer,
it becomes an integer,
if you cast a pointer to a struct,
it becomes a struct.
The pointer can crash...,
and can overflow.
Be a pointer my friend...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d825e0270710030048s3a1633fco9d4d096843aaf5b2>