From: Todd Sayers <tscoltrane@hotmail.com>
To: <gcc-help@gcc.gnu.org>
Subject: make install fails due to "-Wno-overlength-strings"
Date: Thu, 03 Nov 2011 15:34:00 -0000 [thread overview]
Message-ID: <BAY161-W254D7FF91841A3EF9D77EDC4D50@phx.gbl> (raw)
In-Reply-To: <BAY161-W4717513A6F27D971B94EE3C4D50@phx.gbl>
I'm attempting to install gcc 4.3.6 on RHEL 5.5 x86_64 using the installed (default, from Redhat) gcc version 4.1.2. Everything [except the `make install`] appears to work well. Only the `make install` of gcc 4.3.6 fails. It dies with this error:
cc1: error: unrecognized command line option "-Wno-overlength-strings"
gmp,mpfr, and mpc all compiled without error, passed `make check`, and were installed via `make install.` There were no issues. GCC 4.3.6 compiles without error (make) and passes almost 96,000 tests before `make check` dies (after >2hrs using -j4). GCC 4.3.6 was configured
with:
../gcc-4.3.6/configure --prefix=/foo/HPC_apps/AMD --with-gmp-lib=/foo/HPC_apps/AMD/lib --with-gmp-include=/foo/HPC_apps/AMD/include --with-mpfr-include=/foo/HPC_apps/AMD/include --with-mpfr-lib=/foo/HPC_apps/AMD/lib
Please note that (per the instructions) I am NOT building in the source directory. I Googled until I reached the end of the Internet... and, well, after that I decided to write this e-mail. What gives? Is there an environment variable that can be set to force gcc to not attempt to use this option (in the configure logs, it discovers that "-Wno-overlength-strings" is not an available option. WTF?
next parent reply other threads:[~2011-11-03 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY161-W4717513A6F27D971B94EE3C4D50@phx.gbl>
2011-11-03 15:34 ` Todd Sayers [this message]
2011-11-03 22:06 ` Ian Lance Taylor
2011-11-04 2:03 ` Ryan Hill
2011-11-04 14:10 ` Todd Sayers
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=BAY161-W254D7FF91841A3EF9D77EDC4D50@phx.gbl \
--to=tscoltrane@hotmail.com \
--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).