public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Grzegorz Piotr Jaskiewicz <gj@pointblue.com.pl>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: can't compile 2.6.11-rc2 on sparc64
Date: Sun, 23 Jan 2005 02:48:26 +0100	[thread overview]
Message-ID: <200501230248.27332@gj-laptop> (raw)
In-Reply-To: <41F2FFBB.7020300@osdl.org>

On Sunday 23 January 2005 02:36, Randy.Dunlap wrote:

> Please look for another error.  Run 'make' again.
> Those are all just warnings and don't cause a build error.

all output past make:

[root@gjsparc64 linux-2.6.11-rc2]# make V=1
if test ! /usr/src/linux-2.6.11-rc2 -ef /usr/src/linux-2.6.11-rc2; then \
/bin/bash /usr/src/linux-2.6.11-rc2/scripts/mkmakefile              \
    /usr/src/linux-2.6.11-rc2 /usr/src/linux-2.6.11-rc2 2 6         \
    > /usr/src/linux-2.6.11-rc2/Makefile;                                 \
    echo '  GEN    /usr/src/linux-2.6.11-rc2/Makefile';                   \
fi
  CHK     include/linux/version.h
rm -rf .tmp_versions
mkdir -p .tmp_versions
make -f scripts/Makefile.build obj=scripts/basic
make -f scripts/Makefile.build obj=scripts
make -f scripts/Makefile.build obj=scripts/genksyms
make -f scripts/Makefile.build obj=scripts/mod
make -f scripts/Makefile.build obj=init
  CHK     include/linux/compile.h
make -f scripts/Makefile.build obj=usr
set -e; echo '  CHK     usr/initramfs_list'; mkdir -p 
usr/; /bin/bash /usr/src/linux-2.6.11-rc2/scripts/gen_initramfs_list.sh    > 
usr/initramfs_list.tmp; if [ -r usr/initramfs_list ] && cmp -s 
usr/initramfs_list usr/initramfs_list.tmp; then rm -f usr/initramfs_list.tmp; 
else echo '  UPD     usr/initramfs_list'; mv -f usr/initramfs_list.tmp 
usr/initramfs_list; fi
  CHK     usr/initramfs_list
make -f scripts/Makefile.build obj=arch/sparc64/kernel
  /usr/bin/sparc64-pld-linux-gcc -Wp,-MD,arch/sparc64/kernel/.ioctl32.o.d 
-nostdinc -isystem /usr/lib/gcc/sparc64-pld-linux/3.4.2/include -D__KERNEL__ 
-Iinclude  -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing 
-fno-common -ffreestanding -O2     -fomit-frame-pointer -m64 -pipe -mno-fpu 
-mcpu=ultrasparc -mcmodel=medlow -ffixed-g4 -fcall-used-g5 -fcall-used-g7 
-Wno-sign-compare -Wa,--undeclared-regs -finline-limit=100000 
-Wdeclaration-after-statement  -Werror -Ifs/  -DKBUILD_BASENAME=ioctl32 
-DKBUILD_MODNAME=ioctl32 -c -o arch/sparc64/kernel/.tmp_ioctl32.o 
arch/sparc64/kernel/ioctl32.c
include/asm/uaccess.h: In function `siocdevprivate_ioctl':
fs/compat_ioctl.c:648: warning: ignoring return value of `copy_to_user', 
declared with attribute warn_unused_result
fs/compat_ioctl.c: In function `put_dirent32':
fs/compat_ioctl.c:2346: warning: ignoring return value of `copy_to_user', 
declared with attribute warn_unused_result
fs/compat_ioctl.c: In function `serial_struct_ioctl':
fs/compat_ioctl.c:2489: warning: ignoring return value of `copy_from_user', 
declared with attribute warn_unused_result
fs/compat_ioctl.c:2502: warning: ignoring return value of `copy_to_user', 
declared with attribute warn_unused_result
make[1]: *** [arch/sparc64/kernel/ioctl32.o] Error 1
make: *** [arch/sparc64/kernel] Error 2
[root@gjsparc64 linux-2.6.11-rc2]#

I have no idea what causes error here. What shall I input to get more info 
about that error ?
                                       
-- 
GJ

  parent reply	other threads:[~2005-01-23  1:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-23  1:38 can't compile 2.6.11-rc2 on sparc64 Grzegorz Piotr Jaskiewicz
2005-01-23  1:36 ` Randy.Dunlap
2005-01-23  1:45   ` Grzegorz Piotr Jaskiewicz
2005-01-23  1:48   ` Grzegorz Piotr Jaskiewicz [this message]
2005-01-23  2:13     ` Randy.Dunlap
2005-01-23  8:09       ` Grzegorz Piotr Jaskiewicz
2005-01-23  9:08         ` Adrian Bunk

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=200501230248.27332@gj-laptop \
    --to=gj@pointblue.com.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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