From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Kirill Voronin <kvoronin@labchem.sscc.ru>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Problem with building gcc 4.9.0 (libstdc++)
Date: Sun, 10 Aug 2014 17:54:00 -0000 [thread overview]
Message-ID: <CAH6eHdTrc1xO=nD_o++0NpEuaDQyQKpL+unOt-E18+s1tsnAoA@mail.gmail.com> (raw)
In-Reply-To: <a882d1308d7fe3d988ec96bbb2898319.squirrel@mx.sscc.ru>
On 10 August 2014 15:29, Kirill Voronin wrote:
>
>
> Actually, I foolowed the installing instructions and still got the same
> error.
>
> Can anyone please tell me whether Red Hat 4.1.2-46 is compatible
> (supported) by gcc (e.g., 4.9.0 version)?
It should work OK, the errors you're getting do not indicate a problem
with the compiler anyway (they imply mis-configuration).
> The full config.log looks like
>
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
>
> It was created by configure, which was
> generated by GNU Autoconf 2.64. Invocation command line was
>
> $
> /ifs/home/icmmg/voronin/pardiso_proekt/pardiso_project/new/gcc_dir/../gcc-4.9.0/configure
> --prefix=/ifs/home/icmmg/voronin/pardiso_proekt/pardiso_project/new/gcc-4.9.0
> --enable-shared
What directory does the build fail in?
Are you even looking in the right config.log?
http://gcc.gnu.org/wiki/FAQ#configure_suffix explains that you need to
look at config.log in the directory where the build fails.
prev parent reply other threads:[~2014-08-10 17:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 9:54 Kirill Voronin
2014-08-08 9:56 ` Jonathan Wakely
2014-08-08 9:58 ` Jonathan Wakely
2014-08-08 10:22 ` Kirill Voronin
2014-08-08 10:27 ` Jonathan Wakely
2014-08-08 11:13 ` Kirill Voronin
2014-08-08 11:33 ` Jonathan Wakely
2014-08-08 11:38 ` Jonathan Wakely
2014-08-10 11:58 ` Kirill Voronin
2014-08-10 17:43 ` Jonathan Wakely
2014-08-10 12:24 ` Brian Drummond
2014-08-10 14:29 ` Kirill Voronin
2014-08-10 17:54 ` Jonathan Wakely [this message]
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='CAH6eHdTrc1xO=nD_o++0NpEuaDQyQKpL+unOt-E18+s1tsnAoA@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=kvoronin@labchem.sscc.ru \
/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).