GMP Configuration Error

[leif]

Syed Sabah-ud-Din Gilani wrote:
> Dear Sir,
>
> I have installed gmp 5.1.3 successfully on linux based supercomputer but I
> need to configure gmp 4.2.2. I am facing the following error during
> installation of gmp 4.2.2.
>
> g++ -shared -nostdlib
> /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib/crti.o
> /usr/lib/gcc/x86_64-redhat-linux/4.1.2/32/crtbeginS.o  .libs/dummy.o
> cxx/.libs/isfuns.o cxx/.libs/ismpf.o cxx/.libs/ismpq.o cxx/.libs/ismpz.o
> cxx/.libs/ismpznw.o cxx/.libs/osdoprnti.o cxx/.libs/osfuns.o
> cxx/.libs/osmpf.o cxx/.libs/osmpq.o cxx/.libs/osmpz.o  -Wl,--rpath
> -Wl,/export/home2/RCMS/abeera.tariq/gmp-4.2.2/.libs -Wl,--rpath
> -Wl,/export/home2/RCMS/abeera.tariq/local/lib ./.libs/libgmp.so
> -L/usr/lib/gcc/x86_64-redhat-linux/4.1.2/32
> -L/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib -L/lib/../lib
> -L/usr/lib/../lib -lstdc++ -lm -lc -lgcc_s
> /usr/lib/gcc/x86_64-redhat-linux/4.1.2/32/crtendS.o
> /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib/crtn.o  -Wl,-soname
> -Wl,libgmpxx.so.4 -o .libs/libgmpxx.so.4.0.2
> ./.libs/libgmp.so: could not read symbols: File in wrong format
> collect2: ld returned 1 exit status
> make[2]: *** [libgmpxx.la] Error 1
> make[2]: Leaving directory
> `/state/partition1/home2/RCMS/abeera.tariq/gmp-4.2.2'
> make[1]: *** [install-recursive] Error 1
> make[1]: Leaving directory
> `/state/partition1/home2/RCMS/abeera.tariq/gmp-4.2.2'
> make: *** [install] Error 2
> Make Install Successfully
> /export/home2/RCMS/abeera.tariq/local

Looks like a mixture of 64-bit code (libgmp) and 32-bit code for the C++ 
interface / library.  Although I can't really imagine your 'g++' 
defaults to 32-bit, it apparently does.


> Waiting for your positive response and guidelines.

See https://gmplib.org/manual/Reporting-Bugs.html , especially:

    Please include the following in any report,
    ...
    * The ‘configure’ options you used when building GMP, if any.
    * The output from ‘configure’, as printed to stdout, with any 
options used.
    * The name of the compiler and its version. For gcc, get the version 
with ‘gcc -v’, otherwise perhaps ‘what `which cc`’, or similar.
    * The output from running ‘uname -a’.
    * The output from running ‘./config.guess’, and from running 
‘./configfsf.guess’ (might be the same).
    * If the bug is related to ‘configure’, then the compressed contents 
of config.log.
    ...


In your case, also the output of 'g++ -v' would be interesting.

Did you set CFLAGS or CXXFLAGS, or are they set in your environment?


-leif

-- 
() The ASCII Ribbon Campaign
/\   Help Cure HTML E-Mail