public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/48378] gcc 4.6.0 fails to build from source
Date: Sat, 02 Apr 2011 22:52:00 -0000 [thread overview]
Message-ID: <bug-48378-4-amFfPyMuVD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48378-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48378
--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-04-02 22:52:32 UTC ---
(In reply to comment #9)
> (In reply to comment #7)
> > (In reply to comment #6)
> > > I continue to get the originally reported error:
> >
> > It looks as though you continue to build in the source dir, but I can't know
> > for sure as you didn't say how you're running configure.
>
> ../gcc-4.6.0/configure
which is the directory you're building in too, right?
i.e. the same as ./configure
So you're still building in the source directory.
You need TWO directories, one for the sources, and one you build in.
And why are you using with_xxx_lib instead of using --with-gmp ?
Try the makefile at http://advogato.org/person/redi/diary/229.html which will
do it all for you correctly:
make -f config-gcc.mk GCC_VERSION=4.6.0 GMP_VERSION=5.0.1
next prev parent reply other threads:[~2011-04-02 22:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 0:36 [Bug other/48378] New: " nbi at wideopenwest dot com
2011-03-31 10:02 ` [Bug other/48378] " rguenth at gcc dot gnu.org
2011-03-31 11:06 ` redi at gcc dot gnu.org
2011-03-31 17:59 ` nbi at wideopenwest dot com
2011-04-01 3:12 ` nbi at wideopenwest dot com
2011-04-01 8:36 ` redi at gcc dot gnu.org
2011-04-02 21:16 ` nbi at wideopenwest dot com
2011-04-02 21:25 ` redi at gcc dot gnu.org
2011-04-02 21:26 ` redi at gcc dot gnu.org
2011-04-02 22:24 ` nbi at wideopenwest dot com
2011-04-02 22:52 ` redi at gcc dot gnu.org [this message]
2011-04-02 23:18 ` nbi at wideopenwest dot com
2011-04-02 23:26 ` redi at gcc dot gnu.org
2011-04-02 23:32 ` redi at gcc dot gnu.org
2011-04-02 23:40 ` redi at gcc dot gnu.org
2011-04-02 23:42 ` nbi at wideopenwest dot com
2011-04-02 23:44 ` redi at gcc dot gnu.org
2011-04-03 0:14 ` nbi at wideopenwest dot com
2011-04-03 0:21 ` redi at gcc dot gnu.org
2011-04-03 2:48 ` nbi at wideopenwest dot com
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-48378-4-amFfPyMuVD@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: 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).