Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Geoffrey Espin <espin@idiom.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: "Steven J. Hill" <sjhill@cotw.com>, linux-mips@oss.sgi.com
Subject: Re: [PATCH] Compiler warnings and remove unused code....
Date: Wed, 30 Jan 2002 10:39:19 -0800	[thread overview]
Message-ID: <20020130103919.A49140@idiom.com> (raw)
In-Reply-To: <Pine.GSO.3.96.1020130193233.8443D-100000@delta.ds2.pg.gda.pl>; from Maciej W. Rozycki on Wed, Jan 30, 2002 at 07:35:13PM +0100

Maciej,

> > This is linux.2.4.16 + sourceforge/mipslinux (a few weeks old).
>  These errors are not MIPS-specific.  They were introduced by a stricter
> symbol checking in recent binutils.  Many of them (but possibly not all)
> are removed in Linux 2.4.17.  Please try the current version and see if
> they persist.

Thanks!  Thought so. I was afraid of that.  :-)
[Not sure if/when I'll move up again.]

Steve: you might want to add that caveat to your toolchain announcement.

Geoff
-- 
espin@idiom.com

  reply	other threads:[~2002-01-30 19:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 17:29 [PATCH] Compiler warnings and remove unused code Steven J. Hill
2002-01-30 18:23 ` Geoffrey Espin
2002-01-30 18:35   ` Maciej W. Rozycki
2002-01-30 18:39     ` Geoffrey Espin [this message]
2002-01-30 18:46     ` Bradley D. LaRonde
2002-01-30 18:46       ` Bradley D. LaRonde
2002-01-30 18:39   ` James Simmons
2002-01-30 18:44     ` Geoffrey Espin
2002-01-30 18:55       ` James Simmons
2002-01-30 18:41   ` Daniel Jacobowitz
2002-01-30 18:53     ` Geoffrey Espin
2002-01-30 18:55 ` Maciej W. Rozycki
2002-01-30 19:13   ` Steven J. Hill
2002-01-31 12:45     ` Maciej W. Rozycki
2002-01-30 19:15 ` Steven J. Hill

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=20020130103919.A49140@idiom.com \
    --to=espin@idiom.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    --cc=sjhill@cotw.com \
    /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