From: "David S. Miller" <davem@redhat.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: Compile problem on sparc64
Date: Wed, 24 Mar 2004 22:30:28 +0000 [thread overview]
Message-ID: <20040324143028.747af65c.davem@redhat.com> (raw)
In-Reply-To: <1080160367.2309.71.camel@pegasus>
On Wed, 24 Mar 2004 21:32:47 +0100
Marcel Holtmann <marcel@holtmann.org> wrote:
> > > I am using Debian Sid with GCC 3.3.3 (Debian 20040320) and I got the
> > > following error on my sparc64 platform while compiling the latest
> > > Bitkeeper sources from 2.6:
> >
> > This should cure it, let me know if it doesn't.
>
> Seems that this is not enough. Now I get this one:
>
> CC arch/sparc64/kernel/process.o
> arch/sparc64/kernel/process.c: In function `flush_thread':
> arch/sparc64/kernel/process.c:435: warning: use of cast expressions as lvalues is deprecated
I'm not getting these, I wonder why. I'm using something similar
to you for builds:
davem@nuts:/disk1/BK/sparc-2.6$ gcc --version
gcc (GCC) 3.3.3 (Debian)
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
davem@nuts:/disk1/BK/sparc-2.6$
Please also send me your .config under seperate cover if you'd be so
kind, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: "David S. Miller" <davem@redhat.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: Compile problem on sparc64
Date: Wed, 24 Mar 2004 14:30:28 -0800 [thread overview]
Message-ID: <20040324143028.747af65c.davem@redhat.com> (raw)
In-Reply-To: <1080160367.2309.71.camel@pegasus>
On Wed, 24 Mar 2004 21:32:47 +0100
Marcel Holtmann <marcel@holtmann.org> wrote:
> > > I am using Debian Sid with GCC 3.3.3 (Debian 20040320) and I got the
> > > following error on my sparc64 platform while compiling the latest
> > > Bitkeeper sources from 2.6:
> >
> > This should cure it, let me know if it doesn't.
>
> Seems that this is not enough. Now I get this one:
>
> CC arch/sparc64/kernel/process.o
> arch/sparc64/kernel/process.c: In function `flush_thread':
> arch/sparc64/kernel/process.c:435: warning: use of cast expressions as lvalues is deprecated
I'm not getting these, I wonder why. I'm using something similar
to you for builds:
davem@nuts:/disk1/BK/sparc-2.6$ gcc --version
gcc (GCC) 3.3.3 (Debian)
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
davem@nuts:/disk1/BK/sparc-2.6$
Please also send me your .config under seperate cover if you'd be so
kind, thanks.
next prev parent reply other threads:[~2004-03-24 22:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 12:15 Compile problem on sparc64 Marcel Holtmann
2004-03-24 20:19 ` David S. Miller
2004-03-24 20:19 ` David S. Miller
2004-03-24 20:32 ` Marcel Holtmann
2004-03-24 20:32 ` Marcel Holtmann
2004-03-24 22:30 ` David S. Miller [this message]
2004-03-24 22:30 ` David S. Miller
2004-03-24 22:56 ` Marcel Holtmann
2004-03-24 22:56 ` Marcel Holtmann
2004-03-25 20:06 ` David S. Miller
2004-03-25 23:25 ` Marcel Holtmann
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=20040324143028.747af65c.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.