public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bunk at stusta dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/35419] [4.3/4.4 Regression] bfin libgcc build error Date: Tue, 24 Jun 2008 20:20:00 -0000 [thread overview] Message-ID: <20080624201927.17873.qmail@sourceware.org> (raw) In-Reply-To: <bug-35419-9876@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from bunk at stusta dot de 2008-06-24 20:19 ------- Yes, bfin-uclinux works for me. It might be nice to get bfin-linux as an alias for bfin-uclinux, but this bug of mine is definitely INVALID. -- bunk at stusta dot de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35419
prev parent reply other threads:[~2008-06-24 20:20 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-03-02 16:05 [Bug other/35419] New: " bunk at stusta dot de 2008-03-27 22:25 ` [Bug target/35419] " rguenth at gcc dot gnu dot org 2008-04-01 8:28 ` jakub at gcc dot gnu dot org 2008-04-02 13:18 ` bernds_cb1 at t-online dot de 2008-06-06 15:03 ` rguenth at gcc dot gnu dot org 2008-06-24 20:20 ` bunk at stusta dot de [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=20080624201927.17873.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).