On Fri, Feb 26, 2010, Scott Brozell wrote:
>
> While testing this past weekend with pgi i got lots of weird link errors.
> /nfs/10/srb/amber/amber11/bin/nab -c matgen.nab
> /nfs/10/srb/amber/amber11/bin/nab -o matgen matgen.o
> /usr/local/pgi-9.0-1/linux86-64/9.0-1/lib/libpgf90.a(initpar.o): In function `__hpf_abort':initpar.c:(.text+0xc9): undefined reference to `__hpf_abortx'
Here's what is happening: nab is using pgcc to link in code compiled with
pgf90. The configure script assumes that adding "-lpgf90" to the link line
will do it, but that is clearly not working here.
> /usr/local/pgi-9.0-1/linux86-64/9.0-1/lib/libpgf90.a(initpar.o): In function `pghpf_init':
> initpar.c:(.text+0xd6e): undefined reference to `__hpf_init_consts'
The fact that the missing reference is in libpgf90.a indicates that some
additional PG library needs to be added to flibs_arch at about line 466
of configure. A quick survey through the PG lib directory (plus some
searching with "nm") will probably find it.
It is *possible* to use pgf90 to do the link step, but there are a variety of
reasons why I would like to keep the current setup. Probably we should
add a test in configure to make sure that this sort of linking is possible
with the chosen compilers, so that user gets the error message there, rather
than deep inside the build step.
....dac
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Fri Feb 26 2010 - 08:00:02 PST
