public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alexander at mezon dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/51627] cannot compute suffix of object files mipsel
Date: Mon, 19 Dec 2011 21:19:00 -0000 [thread overview]
Message-ID: <bug-51627-4-WI0MCxAgrd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51627-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51627
--- Comment #3 from Alexander Khrukin <alexander at mezon dot ru> 2011-12-19 21:15:06 UTC ---
(In reply to comment #2)
> (In reply to comment #0)
> > checking for suffix of object files... configure: error: in
> > `/home/user/cross-avr-gcc/BUILD/cross-mipsel-gcc-4.6.2/gcc-mipsel/mipsel/libgcc':
> > configure: error: cannot compute suffix of object files: cannot compile
> > See `config.log' for more details.
>
> Have you done this?
>
> Have you read http://gcc.gnu.org/wiki/FAQ#configure_suffix ?
>
> Why not put the gmp, mpfr and mpc sources in the gcc source tree and let it
> build them?
Yeah, im read FAQ but i'm not understand that mpfr and other must be placed
into gcc build dir :3
Thanks for advice.
next prev parent reply other threads:[~2011-12-19 21:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 20:58 [Bug bootstrap/51627] New: " alexander at mezon dot ru
2011-12-19 21:03 ` [Bug bootstrap/51627] " alexander at mezon dot ru
2011-12-19 21:07 ` redi at gcc dot gnu.org
2011-12-19 21:19 ` alexander at mezon dot ru [this message]
2011-12-19 21:20 ` redi at gcc dot gnu.org
2011-12-19 22:29 ` alexander at mezon dot ru
2011-12-19 22:37 ` redi at gcc dot gnu.org
2011-12-19 23:51 ` alexander at mezon dot ru
2011-12-20 0:07 ` pinskia at gcc dot gnu.org
2011-12-20 0:23 ` alexander at mezon dot ru
2011-12-30 6:21 ` pinskia at gcc dot gnu.org
2011-12-30 10:46 ` alexander at mezon dot ru
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-51627-4-WI0MCxAgrd@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).