public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Bo Najdrovsky <bo@tekelec.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/1987: GCC 2.95.2 fails to build under Interix 2.2 Date: Thu, 28 Nov 2002 15:26:00 -0000 [thread overview] Message-ID: <20021120172602.4674.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/1987; it has been noted by GNATS. From: Bo Najdrovsky <bo@tekelec.com> To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: ben.laws@iex.com Subject: Re: bootstrap/1987: GCC 2.95.2 fails to build under Interix 2.2 Date: Wed, 20 Nov 2002 11:19:04 -0600 bangerth@dealii.org wrote: >Synopsis: GCC 2.95.2 fails to build under Interix 2.2 > >State-Changed-From-To: open->feedback >State-Changed-By: bangerth >State-Changed-When: Tue Nov 19 07:57:38 2002 >State-Changed-Why: > This is a rather old bootstrap error. Can you say whether this > still happens with newer versions of gcc? > > Thanks, W. > >http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=1987 > > Honestly, I haven't tried to build it lately, but I suspect that the problem still exists unless the people at Microsoft submitted some major patches to the project. Interix is now known as Services For Unix, and I know that we have been able to get a newer version of the compiler built here inhouse (I believe it was 2.95.3), but I am not familiar with the level of difficulty that was involved in doing so. I am CC'ing the person here that built it. Ben, do you have any comments on this? Bo Najdrovsky bo@iex.com
next reply other threads:[~2002-11-20 17:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-28 15:26 Bo Najdrovsky [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-28 15:27 Wolfgang Bangerth 2002-11-26 1:56 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=20021120172602.4674.qmail@sources.redhat.com \ --to=bo@tekelec.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).