public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: melvin.hadasht@free.fr
Cc: gcc-help@gcc.gnu.org
Subject: Re: [tree-ssa, cvs] spec failure: unrecognized spec option'<'
Date: Sun, 09 Nov 2003 18:46:00 -0000	[thread overview]
Message-ID: <20031109184641.67383.qmail@web41107.mail.yahoo.com> (raw)

Hello

> Ok, thanks for checking: on my pII 266,
> compilation is not instantaneous.

Yeah, gcc compile time isn't exactly spectacular :-)

>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

See this is what's weird, and symptomatic of a broken
installation. For some reason, your 3.3.2 driver is
running the 3.5 compiler. I'm guessing the 3.3.x
driver is less forgiving about spec file typos,
hence...

>gcc: spec failure: unrecognized spec option '<'

If you go to the prefix where you installed 3.3.x, and
do a find on cc1, what do you get? More importantly,
if you run that cc1, what version does it say it is?
Also, what is you $PATH?

>Concerning the ./specs file, removing the >"%<mcpu=*"
is not sufficient, 
>a closing brace "}" must also be adjusted.

Right.

>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?

You can certainly file a bug report, mentioning the
typo in specs, and give the particulars. The other
error your seeing is more likely part of a screwed up
installation (could also be a bug...). 

If you want to find what's causing the bug, you can
try to figure out what makefile rule generates
gcc/specs (in your build directory), and so figuree
out where the original typo comes from. I'll also take
a look this afternoon and see what I can come up
with...

Cheers,

Dara

P.S. Please cc: replies, since I'm not subscribed to gcc-help@...

__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree

             reply	other threads:[~2003-11-09 18:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-09 18:46 Dara Hazeghi [this message]
2003-11-09 21:25 ` Melvin Hadasht
2003-11-10  2:15   ` Dara Hazeghi
2003-11-10 18:19     ` Melvin Hadasht
2003-11-11  7:25       ` Dara Hazeghi
2003-11-13  7:11         ` [tree-ssa, cvs] (cleaner workaround) " Melvin Hadasht
2003-11-14  8:02           ` Dara Hazeghi
2003-11-14 11:54             ` Melvin Hadasht
2003-11-14 16:45               ` Dara Hazeghi
  -- strict thread matches above, loose matches on Subject: below --
2003-11-08 19:27 [tree-ssa, cvs] spec failure: unrecognized spec option '<' Dara Hazeghi
2003-11-08 11:14 Dara Hazeghi
2003-11-08 18:09 ` Melvin Hadasht
2003-11-07 19:53 Melvin Hadasht

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=20031109184641.67383.qmail@web41107.mail.yahoo.com \
    --to=dhazeghi@yahoo.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=melvin.hadasht@free.fr \
    /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).