public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: ganesh gopalasubramanian <gganeshgcc@gmail.com>
Cc: Florent DEFAY <spira.inhabitant@gmail.com>, gcc-help@gcc.gnu.org
Subject: Re: error while x-compiling libgcc2.c
Date: Tue, 31 Mar 2009 14:23:00 -0000	[thread overview]
Message-ID: <m3hc19py8r.fsf@google.com> (raw)
In-Reply-To: <7238340b0903310000i6034b1d3r240e1a510ff01af3@mail.gmail.com> (ganesh gopalasubramanian's message of "Tue\, 31 Mar 2009 12\:30\:55 +0530")

ganesh gopalasubramanian <gganeshgcc@gmail.com> writes:

> We tried building the libraries using the make script and it ended up
> with the error. For debugging we compiled the file (libgcc2.c) in the
> path and it went on fine. Any idea about this situation?

In a normal gcc build, building libgcc is the first time that the newly
built compiler is used.  Bugs in the new compiler normally show up then.
The problem could really be anything.  What it means is that there is
something wrong with your compiler.  You have to debug the problem to
find out what it is.

Ian

  parent reply	other threads:[~2009-03-31 14:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31  6:19 ganesh gopalasubramanian
2009-03-31  6:51 ` Florent DEFAY
2009-03-31  7:01   ` ganesh gopalasubramanian
2009-03-31  7:29     ` Florent DEFAY
2009-03-31  7:47       ` Florent DEFAY
2009-03-31 14:23     ` Ian Lance Taylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-25 15:33 Florent DEFAY
2009-03-25 18:50 ` Georg-Johann Lay

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=m3hc19py8r.fsf@google.com \
    --to=iant@google.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gganeshgcc@gmail.com \
    --cc=spira.inhabitant@gmail.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: 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).