public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/4269: [sparc-unknown-netbsdeld1.5] HAVE_NL_LANGINFO doesn't ensure that CODESET is available
Date: Sat, 30 Nov 2002 20:06:00 -0000	[thread overview]
Message-ID: <20021121113609.6616.qmail@sources.redhat.com> (raw)

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

From: Adrian Bunk <bunk@fs.tum.de>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
  nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/4269: [sparc-unknown-netbsdeld1.5] HAVE_NL_LANGINFO doesn't ensure that CODESET is available
Date: Thu, 21 Nov 2002 12:27:51 +0100

 On Wed, Nov 20, 2002 at 02:25:13AM -0000, bangerth@dealii.org wrote:
 > Old Synopsis: HAVE_NL_LANGINFO doesn't ensure that CODESET is available
 > New Synopsis: [sparc-unknown-netbsdeld1.5] HAVE_NL_LANGINFO doesn't ensure that CODESET is available
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: bangerth
 > State-Changed-When: Tue Nov 19 18:25:13 2002
 > State-Changed-Why:
 >     This is quite an old bootstrap report. Could you please
 >     re-check with a newer version of gcc and report whether
 >     it works or not?
 
 The problem is still present in the files gcc/java/jcf-parse.c and
 gcc/java/jv-scan.c in gcc-3.2.1
 
 >     Thanks
 >       W.
 
 cu
 Adrian
 
 -- 
 
        "Is there not promise of rain?" Ling Tan asked suddenly out
         of the darkness. There had been need of rain for many days.
        "Only a promise," Lao Er said.
                                        Pearl S. Buck - Dragon Seed
 


             reply	other threads:[~2002-11-21 11:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-30 20:06 Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-03 14:06 aph
2003-01-27 18:06 Adrian Bunk
2002-11-27 16:19 bangerth

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=20021121113609.6616.qmail@sources.redhat.com \
    --to=bunk@fs.tum.de \
    --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).