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: bootstrap/4753: [mips] fails to build libgcc for mips target on linux host
Date: Fri, 09 May 2003 09:16:00 -0000 [thread overview]
Message-ID: <20030509091602.23639.qmail@sources.redhat.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]
The following reply was made to PR bootstrap/4753; it has been noted by GNATS.
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: "Frédéric_Pétrot" <Frederic.Petrot@lip6.fr>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/4753: [mips] fails to build libgcc for mips target on linux host
Date: Fri, 9 May 2003 02:12:22 -0700 (PDT)
Hello,
> A simple work around in gcc-3.2 is to comment the
> following line in
> varasm.c
>
> 2012 #if 0
> 2013 /* Fred:
> 2014
>
/dsk/l1/fred/disydent/current/gnu/gcc-3.2.2/gcc/libgcc2.c:62:
> 2015 Internal compiler error in
> assemble_integer, at varasm.c:2013
> 2016 Please submit a full bug report,
> 2017 with preprocessed source if appropriate.
> 2018 */
> 2019
> 2020 if (force)
> 2021 abort ();
> 2022 #endif
>
> I'll move to mipsel-elf (that builds fine), since
> this is
> «~le sens de l'Histoire~».
> Thnaks anyway for keeping me informed.
No problem. Thanks for the response.
Dara
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
next reply other threads:[~2003-05-09 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 9:16 Dara Hazeghi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-09 8:16 Frédéric Pétrot
2003-05-08 10:55 giovannibajo
2003-05-08 3:16 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=20030509091602.23639.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: 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).