public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org To: drk@sgi.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, johnv@adacel.com.au, ro@TechFak.Uni-Bielefeld.DE, nobody@gcc.gnu.org Subject: Re: c++/3047: g++ does not define _LANGUAGE_C_PLUS_PLUS needed for <signal.h> on IRIX Date: Thu, 14 Jun 2001 20:53:00 -0000 [thread overview] Message-ID: <20010615035309.29133.qmail@sourceware.cygnus.com> (raw) Synopsis: g++ does not define _LANGUAGE_C_PLUS_PLUS needed for <signal.h> on IRIX State-Changed-From-To: open->feedback State-Changed-By: rodrigc State-Changed-When: Thu Jun 14 20:53:09 2001 State-Changed-Why: Can you try a snapshot of gcc 3.0 available from: http://www.codesourcery.com/gcc-snapshots.html and see if the problem as been solved under IRIX? http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3047&database=gcc
next reply other threads:[~2001-06-14 20:53 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-14 20:53 rodrigc [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-15 10:44 ro 2001-06-05 5:36 Rainer Orth 2001-06-04 8:06 drk
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=20010615035309.29133.qmail@sourceware.cygnus.com \ --to=rodrigc@gcc.gnu.org \ --cc=drk@sgi.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=johnv@adacel.com.au \ --cc=nobody@gcc.gnu.org \ --cc=ro@TechFak.Uni-Bielefeld.DE \ /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).