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: target/10743: Build error for CPP when building Cross compiler and host and target have diff character sets (i370)
Date: Wed, 14 May 2003 06:36:00 -0000	[thread overview]
Message-ID: <20030514063600.16075.qmail@sources.redhat.com> (raw)

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

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: ivan@vmfacility.fr, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: target/10743: Build error for CPP when building Cross compiler and host and target have diff character sets (i370)
Date: Tue, 13 May 2003 23:29:16 -0700

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 trail&database=gcc&pr=10743
 
 Hello,
 
 looking at the "supported system" list for gcc, I see "This port is  
 very preliminary and has many known bugs.  We hope to have a  
 higher-quality port for this machine soon." Not very encouraging.  
 Still, if you want to pursue this bug, I suggest that you try out the  
 latest gcc cvs and see how it fairs. Neil Booth (our cpp maintainer)  
 has been doing a lot of work to make cpp more robust wrt character sets  
 and the like, and I suspect that if you try out mainline, and have  
 feedback to give him, he might be able to fix the issue. In any case,  
 3.2 branch is dead at this point, so you'll have to try a newer version  
 at some point anyway. Cheers,
 
 Dara
 


             reply	other threads:[~2003-05-14  6:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14  6:36 Dara Hazeghi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-12  9:36 ivan

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=20030514063600.16075.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).