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: c++/7338: Error message contains newline, breaks grep -v; warning from include/g++-v3/bits/stl_threads.h Date: Wed, 17 Jul 2002 12:46:00 -0000 [thread overview] Message-ID: <20020717194602.26111.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7338; it has been noted by GNATS. From: Phil Edwards <phil@jaj.com> To: sampo@symlabs.com Cc: nathan@gcc.gnu.org, gcc-bugs@gcc.gnu.org, miguel@symlabs.com, gcc-gnats@gcc.gnu.org Subject: Re: c++/7338: Error message contains newline, breaks grep -v; warning from include/g++-v3/bits/stl_threads.h Date: Wed, 17 Jul 2002 15:45:43 -0400 On Wed, Jul 17, 2002 at 03:40:22PM +0000, sampo@symlabs.com wrote: > nathan@gcc.gnu.org writes: > > Synopsis: Error message contains newline, breaks grep -v; warning from include/g++-v3/bits/stl_threads.h > > > > State-Changed-From-To: open->closed > > State-Changed-By: nathan > > State-Changed-When: Wed Jul 17 06:21:44 2002 > > State-Changed-Why: > > read about -fmessage-length, you want -fmessage-length=0 > > Thanks for this tidbit, but how about the warning in the stl_threads.h? This is in a FAQ somewhere, but: it's specific to Solaris 2.6, and it's a problem in their thread header files. Sun fixed the problem in later versions of Solaris but has no plans to backport the fix. (It's just adding some punctuation, but oh well.) 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-07-17 19:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-17 12:46 Phil Edwards [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-07-17 15:56 sampo 2002-07-17 11:46 sampo 2002-07-17 9:36 Gabriel Dos Reis 2002-07-17 8:46 sampo 2002-07-17 6:21 nathan 2002-07-17 5:56 sampo
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=20020717194602.26111.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).