public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/7750: [sco] Cannot compile gcc-3.1.1 or gcc-3.2 (fwd) Date: Mon, 28 Apr 2003 23:06:00 -0000 [thread overview] Message-ID: <20030428230601.28861.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/7750; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ices.utexas.edu> To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: bootstrap/7750: [sco] Cannot compile gcc-3.1.1 or gcc-3.2 (fwd) Date: Mon, 28 Apr 2003 18:02:29 -0500 (CDT) ---------- Forwarded message ---------- Date: Mon, 28 Apr 2003 15:55:31 -0700 (PDT) From: Doug Chinnery <doug.chinnery@zadall.com> To: bangerth@ices.utexas.edu Subject: Re: bootstrap/7750: [sco] Cannot compile gcc-3.1.1 or gcc-3.2 => => => > Haven't yet tried anything newer than 3.2.2. => => Did it work for 3.2.2? Not without a patch/hack to some module that now escapes me. I will download and attempt to compile 3.2.3 and give you the results in a couple of hours.
next reply other threads:[~2003-04-28 23:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-28 23:06 Wolfgang Bangerth [this message] 2003-04-29 0:16 Wolfgang 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=20030428230601.28861.qmail@sources.redhat.com \ --to=bangerth@ices.utexas.edu \ --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).