Re: make check returns error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



ad:
[ Charset ISO-8859-1 converted... ]
> Tom Browder wrote:
> >You should try rebuilding OUTSIDE the gcc source tree per the
> >installation instructions.
> 
> Today i've tried that. But didn't help. Get same error message.
> 
> 
> Tim Prince wrote:
> >It looks like you don't have the current mpfr library path set. I've found it 
> >difficult to work with multiple mpfr versions, so I simply replace both 
> >static and dynamic mpfr libraries.
> 
> I was thinking about that also. But i wanted to do it in a clean way. So I 
> tried uninstalling the old libmpfr and using the command line parameters:
> 
> --with-mpfr=pathname
> --with-mpfr-include=pathname
> --with-mpfr-lib=pathname
> 
> Still gcc doesn't see the new lib. Seems like gcc is using the old lib 
> location by default which doesn't have mpfr_remainder() function. That created
> the previous errors from my first post.
> 
> 
> Changes from versions 2.2.* to version 2.3.0(from mpfr homepage)
>    ......
>     * New functions mpfr_j0, mpfr_j1, mpfr_jn, mpfr_y0, mpfr_y1,                                                                
>        mpfr_yn ,mpfr_lgamma, mpfr_remainder, mpfr_remquo, mpfr_fms, 
>        mpfr_signbit, mpfr_setsign, mpfr_copysign, 	mpfr_get_patches.
>     * Functions mpfr_sin, mpfr_cos and mpfr_sin_cos improved (argument 
>        reduction).
>     ......
> 
> 
> i think gcc needs to respect the location and CL parameters that refer to new 
> libmpfr. Is  there anyway to force the  compilation process to recognize the 
> new path without creating symbolic link(even if it means modifying the 
> source)? By the way I get following error in config.log during `make` after 
> uninstalling old mpfr:
> 
> 
> 
> 
> checking for 
> i686-pc-linux-gnu-gcc... /home/ad/build_gcc/./gcc/xgcc -B/home/ad/build_gcc/./gcc/ -B/opt/gcc-4.3.1/i686-pc-linux-gnu/bin/ -B/opt/gcc-4.3.1/i686-pc-linux-gnu/lib/ -isystem /opt/gcc-4.3.1/i686-pc-linux-gnu/include -isystem /opt/gcc-4.3.1/i686-pc-linux-gnu/sys-include
> checking for suffix of object files... configure: error: cannot compute suffix 
> of object files: cannot compile
> See `config.log' for more details.
> make[2]: *** [configure-stage1-target-libgcc] Error 1
> make[2]: Leaving directory `/home/ad/build_gcc'
> make[1]: *** [stage1-bubble] Error 2
> make[1]: Leaving directory `/home/ad/build_gcc'
> make: *** [all] Error 2
> 
> 
> And:
> 
> configure:2567: checking for suffix of object files
> configure:2588: /home/ad/build_gcc/./gcc/xgcc -B/home/ad/build_gcc/./gcc/ -B/opt/gcc-4.3.1/i686-pc-linux-gnu/bin/ -B/opt/gcc-4.3.1/i686-pc-linux-gnu/lib/ -isystem /opt/gcc-4.3.1/i686-pc-linux-gnu/include -isystem /opt/gcc-4.3.1/i686-pc-linux-gnu/sys-include -c -g -fkeep-inline-functions  
> conftest.c >&5
> /home/ad/build_gcc/./gcc/cc1: error while loading shared libraries: 
> libmpfr.so.1: cannot open shared object file: No such file or directory
> configure:2591: $? = 1
> configure: failed program was:
> | /* confdefs.h.  */
> | 
> | #define PACKAGE_NAME "GNU C Runtime Library"
> | #define PACKAGE_TARNAME "libgcc"
> | #define PACKAGE_VERSION "1.0"
> | #define PACKAGE_STRING "GNU C Runtime Library 1.0"
> | #define PACKAGE_BUGREPORT ""
> | /* end confdefs.h.  */
> | 
> | int
> | main ()
> | {
> | 
> |   ;
> |   return 0;
> | }
> configure:2605: error: cannot compute suffix of object files: cannot compile
> See `config.log' for more details.

My GNU/Linux distribution doesn't have a libgmp package at all, and
I'm not certain at all in which directory the distribution hid the
mpfr include files.  The GCC config normally checks for the library
versions.  I'd pursue that as a bug if it's possible to determine
where the check occurs during a proper configuration. 

It's easier to build the libraries as a unit, following the directions
in the source packages.

Since building from the source distributions and installing in
/usr/local (remembering to do "make check" on libmpfr itself and then
setting LD_LIBRARY_PATH, or ld.so.conf, etc.), I haven't had any
problems that were caused by the distros' packages.

Regards,

Robert Kiesling



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux