From: Melvin Hadasht <melvin.hadasht@free.fr>
To: gcc-help@gcc.gnu.org
Subject: Re: Re: [tree-ssa, cvs] spec failure: unrecognized spec option '<'
Date: Sun, 09 Nov 2003 17:08:00 -0000 [thread overview]
Message-ID: <etPan.3fae318f.520eedd1.a27@freefluid> (raw)
In-Reply-To: <20031108192720.93757.qmail@web41101.mail.yahoo.com>
Hi,
> I just checked on mainline cvs, and the same problem's
> there. However on 3.3 branch it looks fine. I'm
> guessing this was introduced when Neil rewrotes
> specs/options handling on mainline.
Ok, thanks for checking: on my pII 266, compilation is not instantaneous.
>P.S. I'm still puzzled with the error you get though
> (I see nothing)...
I searched google and the archive, and I did not found anyone having the
same problem. So it seems I have a broken system.
I "echo"ed the offending command line (given in my last post), to do
env-var expansion and added the -v switch to the resulting gcc command,
and run it and I found this:
Reading specs from ./specs
Configured with: /usr/local/src/cvs/gcc-3.3.2/configure
Thread model: posix
gcc driver version 3.3.2 executing gcc version 3.5-tree-ssa
gcc: spec failure: unrecognized spec option '<'
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/cc1 -quiet -v -I. -I. -I/usr/local/src/cvs/gcc/gcc -I/usr/local/src/cvs/gcc/gcc/. -I/usr/local/src/cvs/gcc/gcc/../include -I/usr/local/src/cvs/gcc/gcc/../libbanshee/libcompat -I/usr/local/src/cvs/gcc/gcc/../libbanshee -I/usr/local/src/cvs/gcc/gcc/../libbanshee/points-to -DIN_GCC -DHAVE_CONFIG_H -DSTANDARD_STARTFILE_PREFIX="../../../" -DSTANDARD_EXEC_PREFIX="/usr/local/gcc-ssa/lib/gcc/" -DSTANDARD_LIBEXEC_PREFIX="/usr/local/gcc-ssa/libexec/gcc/" -DDEFAULT_TARGET_VERSION="3.5-tree-ssa" -DDEFAULT_TARGET_MACHINE="i686-pc-linux-gnu" -DSTANDARD_BINDIR_PREFIX="/usr/local/gcc-ssa/bin/" -DTOOLDIR_BASE_PREFIX="../../../../" /usr/local/src/cvs/gcc/gcc/fortran/gfortranspec.c mcpu=* -quiet -dumpbase gfortranspec.c -auxbase gfortranspec -O -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -version -fno-common -o .s
cc1: error: output filename specified twice
GNU C version 3.3.2 (i686-pc-linux-gnu)
compiled by GNU C version 3.3.2.
GGC heuristics: --param ggc-min-expand=38 --param ggc-min-heapsize=15861
The "mcpu=*" gives cc1: error: bad value (*) for -mcpu= switch. Which I suppose
is the result of the ./specs file being incorrect.
(Note that for this test I reconfigured without c++, thus here it is compiling gfortranspec.c
and not g++spec.c)
Concerning the ./specs file, removing the "%<mcpu=*" is not sufficient,
a closing brace "}" must also be adjusted.
I don't have any idea on how to find where the problem is, but I'm willing to do any tests.
Should I file a bug report?
If I understand you well, there are two problems:
i) the incorrect specs file (for which I would file a bug) which is seen also in other systems and
ii) my system that issues the error while your does not.
Thanks.
prev parent reply other threads:[~2003-11-09 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-08 19:27 Dara Hazeghi
2003-11-09 17:08 ` Melvin Hadasht [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=etPan.3fae318f.520eedd1.a27@freefluid \
--to=melvin.hadasht@free.fr \
--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).