public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kirill Voronin" <kvoronin@labchem.sscc.ru>
To: gcc-help@gcc.gnu.org
Subject: Re: Re: Re: Problem with building gcc 4.9.0 (libstdc++)
Date: Sun, 10 Aug 2014 11:58:00 -0000	[thread overview]
Message-ID: <305b01afb342b77581318044d19caa12.squirrel@mx.sscc.ru> (raw)
In-Reply-To: <CAH6eHdSJhCR1+wgWONXYHHssNRz1Tcff3JYR6C28oxkmOSY_8w@mail.gmail.com>


Yes, the symbolic links called "gmp", "mpfr" and
"mpc" in the gcc-4.9.0 source directory are present.

I foolowed instructions from the installation guide

https://gcc.gnu.org/wiki/InstallingGCC

directly, but nevertheless got the following error (in config.log) when
doing make (after successful configure)

configure:4970: checking whether g++ accepts -static-libstdc++ -static-libgcc
configure:4987: g++ -o conftest -g -O2   -static-libstdc++ -static-libgcc
conftest.cpp  >&5
g++: unrecognized option '-static-libstdc++'
conftest.cpp:11:2: error: #error -static-libstdc++ not implemented
configure:4987: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| /* end confdefs.h.  */
|
| #if (__GNUC__ < 4) || (__GNUC__ == 4 && __GNUC_MINOR__ < 5)
| #error -static-libstdc++ not implemented
| #endif
| int main() {}

The configure coomand was like

./contrib/download_prerequisites
$PWD/../gcc-4.9.0/configure
--prefix=/ifs/home/icmmg/voronin/pardiso_proekt/pardiso_project/new/gcc-4.9.0
--enable-shared

How should I solve the problem?

Best regards,

Kirill Voronin

> On 8 August 2014 12:33, Jonathan Wakely wrote:
>> On 8 August 2014 12:13, Kirill Voronin wrote:
>>>
>>> OK, thanks for you responses.
>>>
>>> Can you please make it a bit more clear about how to build gcc after
>>> using
>>> download_prerequisites script ?
>>
>> I don't know what isn't clear about the steps at the bottom of the
>> http://gcc.gnu.org/wiki/InstallingGCC page.
>
> "Alternatively, after extracting the GCC source archive, simply run
> the ./contrib/download_prerequisites script in the GCC source
> directory."
>
> Note "in the GCC source directory", not in the GCC build directory,
> not in the contrib sub-directory of the GCC source directory, not
> anywhere else.
>
> After doing that you should have symlinks called "gmp", "mpfr" and
> "mpc" in the gcc-4.9.0 source directory - are they present?
>


-- 


  reply	other threads:[~2014-08-10 11:58 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 [this message]
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

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=305b01afb342b77581318044d19caa12.squirrel@mx.sscc.ru \
    --to=kvoronin@labchem.sscc.ru \
    --cc=gcc-help@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).