public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/5492: basic_string seems to fail to use template-defined allocator. Date: Fri, 19 Apr 2002 13:06:00 -0000 [thread overview] Message-ID: <20020419200606.28376.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/5492; it has been noted by GNATS. From: Phil Edwards <phil@jaj.com> To: gcc-gnats@gcc.gnu.org Cc: bkoz@redhat.com, carlo@alinoe.com, kk71878@hotmail.com, gcc-bugs@gcc.gnu.org Subject: Re: libstdc++/5492: basic_string seems to fail to use template-defined allocator. Date: Fri, 19 Apr 2002 16:01:03 -0400 The two files attached to the audit trail aren't self-contained. So I downloaded post-1.35, and the file stltest.cxx compiles fine for me using 3.1 prerelease. It runs without printing any error messages. There aren't any instructions on what exactly I'm supposed to look for to tell whether it's working, so I don't know whether it works or not. It creates a file called "teststl.odb" but then doesn't do anything with it. None of the other binaries built during installation do anything with it either. Phil -- If ye love wealth greater than liberty, the tranquility of servitude greater than the animating contest for freedom, go home and leave us in peace. We seek not your counsel, nor your arms. Crouch down and lick the hand that feeds you; and may posterity forget that ye were our countrymen. - Samuel Adams
next reply other threads:[~2002-04-19 20:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-19 13:06 Phil Edwards [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-31 18:36 pme 2002-04-20 16:55 bkoz 2002-04-19 13:36 Benjamin Kosnik 2002-04-04 19:46 Kevin Killingsworth 2002-04-04 11:51 bkoz 2002-01-27 10:15 rodrigc
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=20020419200606.28376.qmail@sources.redhat.com \ --to=phil@jaj.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: linkBe 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).