From: Mikael Pettersson <mikpe@csd.uu.se>
To: "Norman Diamond" <ndiamond@wta.att.ne.jp>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test5, gcc 3.3, aic7(censored)_core.c
Date: Mon, 29 Sep 2003 12:48:11 +0200 [thread overview]
Message-ID: <16248.3563.675576.448898@gargle.gargle.HOWL> (raw)
In-Reply-To: <2ff401c38611$5ef13d20$44ee4ca5@DIAMONDLX60>
Norman Diamond writes:
> In 2.6.0-test5, the README still says "Make sure you have gcc 2.95.3
> available." It is telling the truth.
>
> SuSE 8.2 includes gcc 3.3 20030226 (prerelease). Up to the point of
> aborting, it diagnoses a ton of "warning: comparison between signed and
> unsigned", but nonetheless compiles many source files and continues. But in
> aic7(censored)_core.c, line 76, it diagnoses "warning: `num_chip_names'
> defined but not used". Even though this is also just a warning, obviously
> it threatens disastrous consequences :-s (sarcasm). make[3] quits with
> Error 1 and make[2] and make[1] quit with Error 2.
Look for and delete any -Werror in aic7xxx' Makefile.
I've seen people being bit by this before.
prev parent reply other threads:[~2003-09-29 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 22:38 Norman Diamond
2003-09-29 10:48 ` Mikael Pettersson [this message]
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=16248.3563.675576.448898@gargle.gargle.HOWL \
--to=mikpe@csd.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=ndiamond@wta.att.ne.jp \
/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
all inboxes | Powered by JetHome®