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: Sat, 08 Nov 2003 11:14:00 -0000 [thread overview]
Message-ID: <20031108111453.7423.qmail@web41112.mail.yahoo.com> (raw)
Hello,
looks like you found a bug. For me though, I only see
it by visual inspection, ie I don't get any error
building. Still, it looks like a bug in either case.
File a report through bugzilla (or I will, if I get a
chance). Thanks,
Dara
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
next reply other threads:[~2003-11-08 11:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-08 11:14 Dara Hazeghi [this message]
2003-11-08 18:09 ` Melvin Hadasht
-- strict thread matches above, loose matches on Subject: below --
2003-11-09 18:46 [tree-ssa, cvs] spec failure: unrecognized spec option'<' Dara Hazeghi
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-08 19:27 [tree-ssa, cvs] spec failure: unrecognized spec option '<' Dara Hazeghi
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=20031108111453.7423.qmail@web41112.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).