public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rt@takagi-ryo.ac
To: bkoz@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/2691
Date: Fri, 04 May 2001 04:46:00 -0000	[thread overview]
Message-ID: <20010504114604.7180.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR libstdc++/2691; it has been noted by GNATS.

From: rt@takagi-ryo.ac
To: bkoz@gcc.gnu.org
Cc: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: libstdc++/2691
Date: Fri, 04 May 2001 20:31:52 +0900 (JST)

 Thank you for the reply.
 
 From: bkoz@gcc.gnu.org
 Subject: Re: libstdc++/2691
 Date: 30 Apr 2001 16:35:54 -0000
 Message-ID: <20010430163554.8759.qmail@sourceware.cygnus.com>
 
 >     I've boiled down your testcase to this:
 >     
 >     #include <iostream>
 >     
 >     using namespace std;
 >     
 >     int main()
 >     {
 >       cerr << "test message\n";
 >       wcerr << L"test message\n";
 >     }
 > which works fine with current CVS sources. Can you try the
 > codesourcery CVS gcc webpage and confirm?
 
   I have compiled the newest GCC source (May 2 snapshot) from the CVS
 and tried, and the result was:
 
 1) configuring with options:
      --prefix=/usr/local/gcc014 --enable-languages=c,c++
      --enable-cstdio=libio --enable-clocale=gnu --enable-c-mbchar
    -> Segmentation fault
 
 2) configuring with options:
      --prefix=/usr/local/gcc014 --enable-languages=c,c++
      --enable-shared
    -> Successful
 
   Excuse me for sending pre-processed output.
 
   With best regards,
 ---
 R Takagi (rt@takagi-ryo.ac)


             reply	other threads:[~2001-05-04  4:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-04  4:46 rt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-08 23:46 libstdc++/2691 bkoz
2001-05-04  8:56 libstdc++/2691 Benjamin Kosnik
2001-04-30  9:36 libstdc++/2691 bkoz

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=20010504114604.7180.qmail@sourceware.cygnus.com \
    --to=rt@takagi-ryo.ac \
    --cc=bkoz@gcc.gnu.org \
    --cc=gcc-prs@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).