From: Dara Hazeghi <dhazeghi@yahoo.com>
To: Melvin Hadasht <melvin.hadasht@free.fr>
Cc: gcc-help@gcc.gnu.org
Subject: Re: [tree-ssa, cvs] spec failure: unrecognized spec option'<'
Date: Mon, 10 Nov 2003 02:15:00 -0000 [thread overview]
Message-ID: <20031110021544.52904.qmail@web41102.mail.yahoo.com> (raw)
In-Reply-To: <etPan.3faea8e4.614fd4a1.2ebe@freefluid>
Hello,
> I did some more tests:
> Configuring with --enable-languages=c (without c++
> or f95), and doing
> a make (no bootstrap) compiles correctly (but the
> specs did have the bug).
> I'm currently doing a bootstrap to test. (I'm still
> using tree-ssa from
> cvs 2003-11-07 13:20 UTC)
So here's a question. If you can get it to the point
where it fails again, would you mind running that
final failing commandline, but gradually trimming off
options, and experimenting, to see what it can be
reduced to? Hopefully this won't require a full
bootstrap...
I think this approach is most likely to find out why
the 3.3 driver is invoking the newly built 3.5
compiler.
Oh, as for the typo, I figured out where it was coming
from, and sent a message to the main gcc list.
Hopefully somebody will apply a patch for it soon (if
not I'll open a bug report to remind them).
Cheers,
Dara
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
next prev parent reply other threads:[~2003-11-10 2:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-09 18:46 Dara Hazeghi
2003-11-09 21:25 ` Melvin Hadasht
2003-11-10 2:15 ` Dara Hazeghi [this message]
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=20031110021544.52904.qmail@web41102.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).