Your suggestion was excellent. I couldn't apply it, for various
reasons, to our 64-bit dual opteron machine, but I did download and
apply it to a 32-bit machine. I then reran the test problem, using
gfortran 4.3, and found that the problem still persists. I have a
fair idea of what is causing the problem; it has to do with my usage
of optional arguments.
As long as I compile on the machine that I installed gfortran 4.3 on,
everything works fine. However, if I attempt to compile, using the
new install, from another machine, it complains about a missing
library:
(bash) robocomp.pts/6% make -f Make_p_713_gf43
mpif77 -g -fbounds-check -I/usr/include -c common_parameters.f90
mpif77 -g -fbounds-check -I/usr/include -c shared_common_parent.f90
mpif77 -g -fbounds-check -I/usr/include -c utilities_parent.f90
mpif77 -g -fbounds-check -I/usr/include -c error_handler.f90
mpif77 -g -fbounds-check -I/usr/include -c make_partition_parent.f90
mpif77 -g -fbounds-check -I/usr/include -c MS_partition_parent.f90
mpif77 -g -fbounds-check -I/usr/include -c reorder_parent.f90
mpif77 -g -fbounds-check -I/usr/include -c MS_PCG_parent.f90
mpif77 -g -fbounds-check -I/usr/include -c driver_linear.f90
mpif77 -g -fbounds-check -I/usr/include -c elapsed_time_function.f90
mpif77 -o parent_713_gf43.ex driver_linear.o elapsed_time_function.o error_handler.o common_parameters.o shared_common_parent.o utilities_parent.o make_partition_parent.o MS_partition_parent.o reorder_parent.o MS_PCG_parent.o -L/z/niwot/home/rlnaff/usr/irun/lib -g -fbounds-check -I/usr/include
/usr/bin/ld: cannot find -laio
collect2: ld returned 1 exit status
make: *** [parent_713_gf43.ex] Error 1
Any ideas?
-- Rich Naff
On Tue, 17 Apr 2007, Milan Hodoscek wrote:
>>>>>> "Rich" == Rich Naff <rlnaff_at_[hidden]> writes:
>
> Rich> As I live in a world where the computer administrator does
> Rich> the upgrades, I am reluctant to ask for upgrades unless I
> Rich> can justify the effort.
>
> I don't see there is a problem here. You can always install whatever
> gcc version you want on your home directory. The instructions to do
> that are really simple. Then you just change the path and you are on
> your own. I suggest you use -static to link the executable, so you can
> run it on any node without the need for extra path or LD_LIBRARY_PATH,
> but that wold work, too.
>
> Welcome to software freedom -- Milan
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
--
Rich Naff
U.S. Geological Survey
MS 413 Box 25046
Denver, CO 80225 USA
telephone: (303) 236-4986
Email: rlnaff_at_[hidden]
|
