public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sliwa at blue dot cft.edu.pl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/49137] build fails when gmp/mpfr already installed Date: Fri, 16 Dec 2011 12:27:00 -0000 [thread overview] Message-ID: <bug-49137-4-BKgKhmLRHn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49137-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49137 --- Comment #2 from Cezary Sliwa <sliwa at blue dot cft.edu.pl> 2011-12-16 12:17:18 UTC --- tar jxf gcc-4.5.3.tar.bz2 tar jxf gmp-4.3.2.tar.bz2 tar jxf mpfr-3.0.0.tar.bz2 tar zxf mpc-0.9.tar.gz patch -p1 -d mpfr-3.0.0 <mpfr-3.0.0-p8.diff cd gcc-4.5.3 ln -s ../gmp-4.3.2 gmp ln -s ../mpfr-3.0.0 mpfr ln -s ../mpc-0.9 mpc cd .. mkdir objdir-4.5.3 cd objdir-4.5.3/ ../gcc-4.5.3/configure --prefix=${HOME}/opt/gcc/4.5.3 --enable-languages=c,c++,fortran gmake fails with: checking for gmp.h... no configure: error: gmp.h can't be found, or is unusable. gmake[2]: *** [configure-stage1-mpfr] Error 1 gmake[2]: Leaving directory `/usr/home/sliwa/src/gcc/objdir-4.5.3' gmake[1]: *** [stage1-bubble] Error 2 gmake[1]: Leaving directory `/usr/home/sliwa/src/gcc/objdir-4.5.3' gmake: *** [all] Error 2 $ ls -l gmp/gmp.h -rw-r--r-- 1 sliwa users 84253 Dec 16 14:12 gmp/gmp.h $ ls -l gmp/.libs/ total 1778 -rw-r--r-- 1 sliwa users 1801182 Dec 16 14:13 libgmp.a lrwxr-xr-x 1 sliwa users 12 Dec 16 14:13 libgmp.la -> ../libgmp.la -rw-r--r-- 1 sliwa users 752 Dec 16 14:13 libgmp.lai
next prev parent reply other threads:[~2011-12-16 12:17 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-24 11:48 [Bug other/49137] New: " sliwa at blue dot cft.edu.pl 2011-12-16 0:37 ` [Bug other/49137] " pinskia at gcc dot gnu.org 2011-12-16 12:27 ` sliwa at blue dot cft.edu.pl [this message] 2022-01-08 10:28 ` [Bug bootstrap/49137] " pinskia at gcc dot gnu.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=bug-49137-4-BKgKhmLRHn@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).