From: Marcel Holtmann <marcel@holtmann.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: SPARC Linux Mailing List <sparclinux@vger.kernel.org>
Subject: Compile problem with sparc64
Date: Wed, 14 Apr 2004 20:15:55 +0000 [thread overview]
Message-ID: <1081973754.3372.5.camel@pegasus> (raw)
Hi,
the changeset
ChangeSet@1.1713.27.238, 2004-04-12 13:31:10-07:00, akpm@osdl.org
[PATCH] binfmt_elf.c fix for 32-bit apps with large bss
causes this compile problem on sparc64
CC arch/sparc64/kernel/binfmt_elf32.o
In file included from arch/sparc64/kernel/binfmt_elf32.c:154:
fs/binfmt_elf.c: In function `load_elf_interp':
fs/binfmt_elf.c:369: warning: comparison is always false due to limited range of data type
fs/binfmt_elf.c: In function `load_elf_binary':
fs/binfmt_elf.c:780: warning: comparison is always false due to limited range of data type
Regards
Marcel
WARNING: multiple messages have this Message-ID (diff)
From: Marcel Holtmann <marcel@holtmann.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: SPARC Linux Mailing List <sparclinux@vger.kernel.org>
Subject: Compile problem with sparc64
Date: Wed, 14 Apr 2004 22:15:55 +0200 [thread overview]
Message-ID: <1081973754.3372.5.camel@pegasus> (raw)
Hi,
the changeset
ChangeSet@1.1713.27.238, 2004-04-12 13:31:10-07:00, akpm@osdl.org
[PATCH] binfmt_elf.c fix for 32-bit apps with large bss
causes this compile problem on sparc64
CC arch/sparc64/kernel/binfmt_elf32.o
In file included from arch/sparc64/kernel/binfmt_elf32.c:154:
fs/binfmt_elf.c: In function `load_elf_interp':
fs/binfmt_elf.c:369: warning: comparison is always false due to limited range of data type
fs/binfmt_elf.c: In function `load_elf_binary':
fs/binfmt_elf.c:780: warning: comparison is always false due to limited range of data type
Regards
Marcel
next reply other threads:[~2004-04-14 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 20:15 Marcel Holtmann [this message]
2004-04-14 20:15 ` Compile problem with sparc64 Marcel Holtmann
2004-04-14 20:22 ` David S. Miller
2004-04-14 20:22 ` David S. Miller
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=1081973754.3372.5.camel@pegasus \
--to=marcel@holtmann.org \
--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 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.