public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Ryan Murray <rmurray@cyberhqz.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/2987: gcc 3.0 0526 fails to build on mips*-linux
Date: Wed, 10 Apr 2002 18:36:00 -0000	[thread overview]
Message-ID: <20020411013601.17702.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/2987; it has been noted by GNATS.

From: Ryan Murray <rmurray@cyberhqz.com>
To: rth@gcc.gnu.org, debian-gcc@lists.debian.org, gcc-bugs@gcc.gnu.org,
        gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/2987: gcc 3.0 0526 fails to build on mips*-linux
Date: Wed, 10 Apr 2002 18:30:09 -0700

 --JP+T4n/bALQSJXh8
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Tue, Apr 09, 2002 at 10:15:33PM -0000, rth@gcc.gnu.org wrote:
 > Synopsis: gcc 3.0 0526 fails to build on mips*-linux
 >=20
 > State-Changed-From-To: analyzed->feedback
 > State-Changed-By: rth
 > State-Changed-When: Tue Apr  9 15:15:32 2002
 > State-Changed-Why:
 >     Something's screwy here with your setup.  <string.h> is=20
 >     included by gcc/tsystem.h iff -Dinhibit_libc is not defined.
 >     Yet your preprocessed file does not include <string.h> and
 >     your presented command line does not include -Dinhibit_libc.
 >    =20
 >     Answer me that?
 
 I can't.  That's the way it was at that point in time.
 
 >     And try again with the 3.1 prerelease.  No one is going to
 >     do anything with 3.0.
 
 And it's been fixed for some time in 3.0...not when it was originally chang=
 ed
 to fixed, but soon afterwards...20020331 cvs of the 3.1 branch builds, so
 I'd say move this one to closed...
 
 --=20
 Ryan Murray, Debian Developer (rmurray@cyberhqz.com, rmurray@debian.org)
 The opinions expressed here are my own.
 
 --JP+T4n/bALQSJXh8
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.6 (GNU/Linux)
 Comment: For info see http://www.gnupg.org
 
 iD8DBQE8tOchN2Dbz/1mRasRAnOXAKD8r8/wfBBfxIiNcnMf3DxvgPktQACg8vvT
 16GB+ni6QAFaDpvhp5OuaSM=
 =vIL+
 -----END PGP SIGNATURE-----
 
 --JP+T4n/bALQSJXh8--


             reply	other threads:[~2002-04-11  1:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10 18:36 Ryan Murray [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-10 23:17 rth
2002-04-09 15:15 rth
2001-06-18 10:38 neil

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=20020411013601.17702.qmail@sources.redhat.com \
    --to=rmurray@cyberhqz.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: link
Be 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).