gmp package installation

[Torbjorn Granlund]

Nastou Panagiotis <pnastou at aegean.gr> writes:

  Recently, I built an rpm package for gmp 5.0.1 for CentOS 5.2 (on an
  HP Proliant Server).  During initial CentOS 5.2 installation, the gmp
  and gmp-devel version 4.1.4 packages were installed.
  
  I tried to update the gmp by command
  
  rpm -Uvh gmp-5.0.1-1.x86_64.rpm
  
These are some sort of packages not done by the GMP team.  We do not
track the many repackagings made by 3rd parties, unfortunately.

  but the update failed because the libgmp.so.3, libgmpxx.so.3 and the
  libmp.so.3 are needed from gcc-gfortran, php, php-cli, guile and
  gmp-devel packages.  Which is the dependency between those packages
  and gmp?  Could I forced update without destroying the operation of
  the above packages?
  
I have no idea.

  Moreover, I read that it is good idea to compile recent versions of
  gmp using gcc versions greater than 4.3.
  
This is not correct advice.  The only unusable GCC release is exactly
4.3.2.  (But one might assume the package creator made sure he/she used
a working compiler, so you should perhaps not worry about this.)

  If gcc, gcc-gfortran and gcc-c++ are updated, and recompile gmp 5.0.1
  could I forced the gmp update?  The other packages (php, php-cli and
  guile) will still operate without problems?
  
You need to ask CentOS, not us.  (Assuming it was CentOS that created
these many packages.)

-- 
Torbjörn