public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: joel@OARcorp.com To: gcc-gnats@gcc.gnu.org Cc: wayne@wmi.com, guerby@acm.org Subject: ada/8344: mips-rtems build problem Date: Thu, 24 Oct 2002 14:56:00 -0000 [thread overview] Message-ID: <20021024215411.31186.qmail@sources.redhat.com> (raw) >Number: 8344 >Category: ada >Synopsis: mips-rtems build problem >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Oct 24 14:56:03 PDT 2002 >Closed-Date: >Last-Modified: >Originator: joel@OARcorp.com >Release: 3.2 and newer >Organization: >Environment: target at least mips-rtems, maybe all embedded mips >Description: See http://gcc.gnu.org/ml/gcc-patches/2002-05/msg01445.html Laurent Guerby submitted a patch for a problem back in May 2002 but it was never acknowledged and since a corresponding PR wasn't filed, it slipped through the cracks. Here is the description: The Ada/mips problem (already discussed with Joel) is that there is a file name conflict between gcc/final.o and gcc/ada/final.o that causes ecoff.h to come wrongly into the picture, the solution is to rename gcc/ada/final.o into something else, here is one patch that renames the gcc/ada source file to adafinal.c. http://gcc.gnu.org/ml/gcc-patches/2002-05/msg01445.html >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-10-24 21:56 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-24 14:56 joel [this message] 2003-01-13 14:25 joel 2003-05-09 19:06 Dara Hazeghi 2003-05-09 19:08 guerby 2003-05-09 19:16 Laurent GUERBY 2003-05-12 13:56 Joel Sherrill
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=20021024215411.31186.qmail@sources.redhat.com \ --to=joel@oarcorp.com \ --cc=gcc-gnats@gcc.gnu.org \ --cc=guerby@acm.org \ --cc=wayne@wmi.com \ /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).