public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/5069: Building libgcc for arm-uclinux target
Date: Tue, 11 Dec 2001 11:46:00 -0000	[thread overview]
Message-ID: <20011211194603.25200.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/5069; it has been noted by GNATS.

From: rodrigc@gcc.gnu.org
To: darmasakti@netscape.com, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org,
  gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: c/5069: Building libgcc for arm-uclinux target
Date: 11 Dec 2001 19:39:44 -0000

 Synopsis: Building libgcc for arm-uclinux target
 
 State-Changed-From-To: open->feedback
 State-Changed-By: rodrigc
 State-Changed-When: Tue Dec 11 11:39:43 2001
 State-Changed-Why:
     Can you try upgrading your Redhat gcc 2.96 version and try
     again?  gcc 2.96-81 has a lot of bugs which have been fixed:
     
     http://lwn.net/2001/0628/a/rh-gcc2.96-rh.php3
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5069&database=gcc


             reply	other threads:[~2001-12-11 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11 11:46 rodrigc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-21 20:55 rodrigc
2001-12-11 11:39 rodrigc
2001-12-11  2:46 darmasakti

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=20011211194603.25200.qmail@sources.redhat.com \
    --to=rodrigc@gcc.gnu.org \
    --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).