public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/6606: [SH]sh-linux compiler fails to build libgcc Date: Sat, 10 May 2003 08:36:00 -0000 [thread overview] Message-ID: <20030510083602.16092.qmail@sources.redhat.com> (raw) The following reply was made to PR target/6606; it has been noted by GNATS. From: Dara Hazeghi <dhazeghi@yahoo.com> To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: target/6606: [SH]sh-linux compiler fails to build libgcc Date: Sat, 10 May 2003 01:33:45 -0700 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- trail&database=gcc&pr=6606 Update: I have successfully built gcc 3.2.3, 3.3 branch, and mainline as i686-linux to sh-linux cross compilers, all of which manage to build mulddi3 without any problem. It appears this bug is probably fixed. Dara
next reply other threads:[~2003-05-10 8:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-10 8:36 Dara Hazeghi [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-10 7:45 giovannibajo 2003-05-10 3:06 Dara Hazeghi
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=20030510083602.16092.qmail@sources.redhat.com \ --to=dhazeghi@yahoo.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).