From: Andrew Morton <akpm@osdl.org>
To: "David S. Miller" <davem@redhat.com>
Cc: cieciwa@alpha.zarz.agh.edu.pl, linux-kernel@vger.kernel.org,
sparclinux@vger.kernel.org
Subject: Re: [SPARC64] kernel 2.6.7+cset-20040625_0611 = ERROR
Date: Fri, 25 Jun 2004 11:53:48 -0700 [thread overview]
Message-ID: <20040625115348.371dcb0b.akpm@osdl.org> (raw)
In-Reply-To: <20040625103020.25b37791.davem@redhat.com>
"David S. Miller" <davem@redhat.com> wrote:
>
> On Fri, 25 Jun 2004 03:05:02 -0700
> Andrew Morton <akpm@osdl.org> wrote:
>
> > "Wojciech 'Sas' Cieciwa" <cieciwa@alpha.zarz.agh.edu.pl> wrote:
> > >
> > > make[1]: *** [arch/sparc64/kernel/process.o] Error 1
> > > make: *** [arch/sparc64/kernel] Error 2
> >
> > here's t'other:
>
> Ok, is it only gcc-3.4 and later that spit out these warnings?
> I've been doing gcc-3.3 builds without incident... oh or maybe
> only on SMP. I haven't tried a uniprocessor build in a while.
I'm using gcc-3.3.2, CONFIG_SMP=y and was able to reproduce the warnings.
prev parent reply other threads:[~2004-06-25 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 11:23 [SPARC64] kernel 2.6.7+cset-20040625_0611 = ERROR Wojciech 'Sas' Cieciwa
2004-06-25 10:04 ` Andrew Morton
2004-06-25 10:05 ` Andrew Morton
2004-06-25 17:30 ` David S. Miller
2004-06-25 18:53 ` Andrew Morton [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=20040625115348.371dcb0b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=cieciwa@alpha.zarz.agh.edu.pl \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.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