This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: undefined reference to _gfortran_set_options
- From: Brian Dessent <brian at dessent dot net>
- To: "Rouson, Damian" <rouson at sandia dot gov>
- Cc: "fortran at gcc dot gnu dot org" <fortran at gcc dot gnu dot org>
- Date: Fri, 24 Oct 2008 19:11:53 -0700
- Subject: Re: undefined reference to _gfortran_set_options
- Organization: My own little world...
- References: <C527C0DC.3C1F%rouson@sandia.gov>
- Reply-to: "fortran at gcc dot gnu dot org" <fortran at gcc dot gnu dot org>
"Rouson, Damian" wrote:
> The parallel
> build links with mpicxx and gives the above error. I'm using a binary of
> gfortran 4.4.0 downloaded about a month ago, but I mpicxx seems to be
> wrapping g++ 4.1.2.
So, essentially you're compiling objects with gfortran 4.4 but trying to
link them with libgfortran 4.1?
> Could this difference in version numbers be causing the
> above problem?
Yes, you can't mix and match like that. They have to correspond.
As I understand it libgfortran starting with 4.3 uses symbol versioning,
which means that it's permissible that the version of libgfortran that
is present at run-time is >= the libgfortran version that was used at
link-time. But that doesn't apply here because A) the libgfortran
version at link-time must still match the version of the compiler used,
and B) it only works in the >= direction, not the < direction. (And it
only works on targets where symbol versioning is supported, of course.)
Brian