public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dtom77 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/36644] make check fails:FAIL: tr1/8_c_compatibility/cmath/functions.cc (test for excess errors)
Date: Fri, 27 Jun 2008 18:13:00 -0000	[thread overview]
Message-ID: <20080627181231.30210.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36644-16388@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from dtom77 at gmail dot com  2008-06-27 18:12 -------
Subject: Re:  make check fails:FAIL: tr1/8_c_compatibility/cmath/functions.cc
(test for excess errors)

On Friday 27 June 2008 06:33, paolo dot carlini at oracle dot com wrote:
>>By the way, I would consider using a 64-bit OS...

I've lots and lots of apps and their configurations. I am not thinking about
transfering right now.

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 which doesn't have mpfr_remainder() function. That creates 
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 
lib. Is  there anyway to force the  compilation process to recognize the new 
path without creating symbolic link (even if it means modifying the source)? I 
can provide assistance regarding this bug. output from config.log during 
`make`:



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.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36644


  parent reply	other threads:[~2008-06-27 18:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26 20:05 [Bug libstdc++/36644] New: " dtom77 at gmail dot com
2008-06-26 20:17 ` [Bug c++/36644] " paolo dot carlini at oracle dot com
2008-06-26 20:49 ` [Bug target/36644] " paolo dot carlini at oracle dot com
2008-06-26 21:27 ` dtom77 at gmail dot com
2008-06-27  5:09 ` dtom77 at gmail dot com
2008-06-27 10:30 ` paolo dot carlini at oracle dot com
2008-06-27 10:33 ` paolo dot carlini at oracle dot com
2008-06-27 10:34 ` paolo dot carlini at oracle dot com
2008-06-27 18:13 ` dtom77 at gmail dot com [this message]
2008-12-28  1:06 ` pinskia at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080627181231.30210.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).