From: "Daniel E. Shipton" <dshipton@vrac.iastate.edu>
To: Dave Jones <davej@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.3-dj2
Date: 04 Feb 2002 10:54:09 -0600 [thread overview]
Message-ID: <1012841649.8335.6.camel@regatta> (raw)
In-Reply-To: <20020204154800.A13519@suse.de>
In-Reply-To: <20020204154800.A13519@suse.de>
2.5.3dj-1 would make bzimage and then die on the modules.....
this is 2.5.3-dj2 and
make bzImage dies and results in the following below........
gcc -D__KERNEL__ -I/home/kernel/linux-2.5/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -DKBUILD_BASENAME=ptrace -c -o ptrace.o ptrace.c
In file included from ptrace.c:13:
/home/kernel/linux-2.5/include/linux/highmem.h: In function `bh_kmap':
/home/kernel/linux-2.5/include/linux/highmem.h:21: dereferencing pointer
to incomplete type
/home/kernel/linux-2.5/include/linux/highmem.h:21: warning: implicit
declaration of function `bh_offset'
/home/kernel/linux-2.5/include/linux/highmem.h: In function `bh_kunmap':
/home/kernel/linux-2.5/include/linux/highmem.h:26: dereferencing pointer
to incomplete type
make[2]: *** [ptrace.o] Error 1
make[2]: Leaving directory `/home/kernel/linux-2.5/kernel'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/home/kernel/linux-2.5/kernel'
make: *** [_dir_kernel] Error 2
next prev parent reply other threads:[~2002-02-04 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 15:48 Linux 2.5.3-dj2 Dave Jones
2002-02-04 16:54 ` Daniel E. Shipton [this message]
2002-02-04 17:36 ` Sebastian Dröge
2002-02-04 18:47 ` Dave Jones
2002-02-04 20:34 ` Daniel E. Shipton
2002-02-04 21:06 ` Dave Jones
2002-02-04 21:04 ` Daniel E. Shipton
2002-02-05 10:55 ` Todor Todorov
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=1012841649.8335.6.camel@regatta \
--to=dshipton@vrac.iastate.edu \
--cc=davej@suse.de \
--cc=linux-kernel@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.