public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rearnsha@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, glenn@caltech.edu, nobody@gcc.gnu.org Subject: Re: target/7079: Won't compile gcc 3.1 for host=i686-pc-linux-gnu, target=arm-linux Date: Thu, 05 Sep 2002 06:27:00 -0000 [thread overview] Message-ID: <20020905132722.22211.qmail@sources.redhat.com> (raw) Synopsis: Won't compile gcc 3.1 for host=i686-pc-linux-gnu, target=arm-linux State-Changed-From-To: open->feedback State-Changed-By: rearnsha State-Changed-When: Thu Sep 5 06:27:20 2002 State-Changed-Why: You don't specify what the failure is. Many people have completed this successfully, so I suspect that it is something you are doing incorrectly rather than a bug in gcc. You appear, for example to have omitted to tell gcc where it can find the header files for an arm-linux system. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7079
next reply other threads:[~2002-09-05 13:27 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-05 6:27 rearnsha [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-31 16:17 rearnsha 2002-06-19 17:06 glenn
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=20020905132722.22211.qmail@sources.redhat.com \ --to=rearnsha@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=glenn@caltech.edu \ --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).