Problems about installing gfortran 4.5 on a remote server

[Runlong Tang <rltang2009 at gmail dot com>]

Hi,

I'd like to install gfortran 4.4 on a remote server/cluster, which
only has gfortran 4.1.2. The reason is that I use gfortran 4.4 on my
personal computer and would like to use the same version on the
server. The system on the server is Red Hat Enterprise Linux Client
release 5.3 (Tikanga), which is from the command cat /etc/*-release.

After downloading the latest gcc 4.4 build under the category 64-bit
AMD-compatible processors (x86_64, AMD64,Intel64, em64t) on the web
page http://gcc.gnu.org/wiki/GFortranBinaries and unpacking it in my
personal directory on the remote server, I went to the bin directory
of of gcc4.4 and tried ./gfortran. It showed the following wrong
information
./gfortran: /lib64/libc.so.6: version `GLIBC_2.11' not found (required
by ./gfortran)
It seems the library libc.so.6 is not new enough. I read the install
instruction, which contains the following words "You may need to
recompile GMP if your GLIBC is too old and you want to use OpenMP ".
So it seems I need to recompile GMP. But I am not familiar with linux
(I mainly a user of MS windows and now only linux to do computations.)
and do not know how to do it, especially on a remote server, where I
am only a user.

I requested the server adminstrator to update gfortran two days ago
but still have not got a response. I think they will response and
might update gfortran. But they might be slow. So I think it would be
better if I can install it by myself as a user. If I can do this, I
can always use the new version of gfortran when I want to without
waiting others to update it.

So the basic question is if it is possible to install gfortran 4.4 on
a server only as a user. If the anwer is yes, then how to do it?

I do not if I have provided the necessary details about the problem. I
hope so and someone can give me some answer in details.

BTW, I'd like to thank the developers of gfortran. It helps my
reseraches on the simulation front.

Thanks,
Runlong