A question about compiling the latest gcc-5.5 on Hpux 11.31 64bit

[uxbeginner22]

I want to compile gcc-5.5 for hpux.

To made 64bit executables.

I had download it,decompress and use this line for configure

./configure --prefix=/opt/gcc64 --with-gmp=/usr/local --with-mpfr=/usr/local --with-mpc=/usr/local LDFLAGS='-L/usr/local/lib'

but give me this errror

checking for the correct version of gmp.h... yes
checking for the correct version of mpfr.h... yes
checking for the correct version of mpc.h... yes
checking for the correct version of the gmp/mpfr/mpc libraries... no
configure: error: Building GCC requires GMP 4.2+, MPFR 2.4.0+ and MPC 0.8.0+.
Try the --with-gmp, --with-mpfr and/or --with-mpc options to specify
their locations.  Source code for these libraries can be found at
their respective hosting sites as well as at
ftp://gcc.gnu.org/pub/gcc/infrastructure/.  See also
http://gcc.gnu.org/install/prerequisites.html for additional info.  If
you obtained GMP, MPFR and/or MPC from a vendor distribution package,
make sure that you have installed both the libraries and the header
files.  They may be located in separate packages.

I have download the correct packages with 64bit,the compiler is hp aCC.

Seems find headers. but not libs.

Any help?Thanks

[ranganath ramachandra]

---

@uxbeginner22wrote:

./configure --prefix=/opt/gcc64 --with-gmp=/usr/local --with-mpfr=/usr/local --with-mpc=/usr/local LDFLAGS='-L/usr/local/lib'

/usr/local/lib houses PA32 libraries. You want /usr/local/lib/hpux64 (on IA64) or /usr/local/lib/pa20_64 (on PA64).

but give me this errror

checking for the correct version of gmp.h... yes
checking for the correct version of mpfr.h... yes
checking for the correct version of mpc.h... yes
checking for the correct version of the gmp/mpfr/mpc libraries... no
configure: error: Building GCC requires GMP 4.2+, MPFR 2.4.0+ and MPC 0.8.0+.
Try the --with-gmp, --with-mpfr and/or --with-mpc options to specify
their locations.  Source code for these libraries can be found at
their respective hosting sites as well as at
ftp://gcc.gnu.org/pub/gcc/infrastructure/.  See also
http://gcc.gnu.org/install/prerequisites.html for additional info.  If
you obtained GMP, MPFR and/or MPC from a vendor distribution package,
make sure that you have installed both the libraries and the header
files.  They may be located in separate packages.

I have download the correct packages with 64bit,the compiler is hp aCC.

Seems find headers. but not libs.

Any help?Thanks

---

Look into the configure log to (possibly) find out where it was searching for the libraries. You might have to add "-v" to LDFLAGS.

List the contents of the packages by file ("swlist -l file <package>") to find out where those libraries are actually installed.

[uxbeginner22]

I did

./configure --prefix=/opt/gcc64 --with-gmp=/usr/local --with-mpfr=/usr/local --with-mpc=/usr/local LDFLAGS='-L/usr/local/lib/hpux64 -v

Of course I have checked library position, with swlist.

But..

checking for the correct version of gmp.h... yes
checking for the correct version of mpfr.h... yes
checking for the correct version of mpc.h... yes
checking for the correct version of the gmp/mpfr/mpc libraries... no
configure: error: Building GCC requires GMP 4.2+, MPFR 2.4.0+ and MPC 0.8.0+.
Try the --with-gmp, --with-mpfr and/or --with-mpc options to specify
their locations.  Source code for these libraries can be found at
their respective hosting sites as well as at
ftp://gcc.gnu.org/pub/gcc/infrastructure/.  See also
http://gcc.gnu.org/install/prerequisites.html for additional info.  If
you obtained GMP, MPFR and/or MPC from a vendor distribution package,
make sure that you have installed both the libraries and the header
files.  They may be located in separate packages.

On config.log I see no errors.

[ranganath ramachandra]

---

On config.log I see no errors.

---

You'll have to really look for anything that might indicate whether the LDPATH you set was indeed used by the linker. E.g. locating that message or the name of one of those libraries in the log file might help. The message seems to be more about versions than the libraries themselves (or it's simply that ambiguous).