From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: linux-kernel@vger.kernel.org
Subject: 2.2.18-24 with IPVS patch has compile errors
Date: Sun, 3 Dec 2000 17:52:26 -0700 [thread overview]
Message-ID: <20001203175226.B24652@vger.timpanogas.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]
With the 2.2.17 IPVS patch applied to 2.2.18-24, I am seeing the following
compile errors.
-D__KERNEL__ -I/usr/src/ute/BUILD/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -D__SMP__ -pipe -fno-strength-reduce
-m386 -DCPU=386 -DMODULE -DMODVERSIONS -include /usr/src/ute/BUILD/linux/include/linux/modversions.h -c -o emd.o emd.c
cc -D__KERNEL__ -I/usr/src/ute/BUILD/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -D__SMP__ -pipe -fno-strength-reduce
-m386 -DCPU=386 -DMODULE -DMODVERSIONS -include /usr/src/ute/BUILD/linux/include/linux/modversions.h -c -o check.o check.c
cc -D__KERNEL__ -I/usr/src/ute/BUILD/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -D__SMP__ -pipe -fno-strength-reduce
-m386 -DCPU=386 -DMODULE -DMODVERSIONS -include /usr/src/ute/BUILD/linux/include/linux/modversions.h -c -o fsync.o fsync.c
touch: /usr/src/ute/BUILD/linux/include/linux/sdladrv.h: No such file or directory
make[2]: *** No rule to make target `/usr/src/ute/BUILD/linux/include/linux/sdlasfm.h', needed by `sdladrv.o'. Stop.
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [/usr/src/ute/BUILD/linux/include/linux/sdladrv.h] Error 1
shell-init: could not get current directory
job-working-directory: could not get current directory
The IPVS patch is also attached. They would seem to be unrelated, but
2.2.18-23 builds clean with this patch.
Jeff
[-- Attachment #2: ipvs-0.9.16-2.2.17.patch.gz --]
[-- Type: application/octet-stream, Size: 36977 bytes --]
next reply other threads:[~2000-12-04 0:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-04 0:52 Jeff V. Merkey [this message]
2000-12-04 1:01 ` Jeff V. Merkey
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=20001203175226.B24652@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®