From: James Pattinson <jamesp@foobarhouse.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] 1.0.1-rc2 config & kernel question
Date: Thu, 20 Sep 2001 15:51:57 +0100 (BST) [thread overview]
Message-ID: <1000997517.3baa028d1105c@mail.foobarhouse.com> (raw)
In-Reply-To: <20010920083116.C551@tykepenguin.com>
Hi!
I've just downloaded LVM 1.0.1-rc2 and tried to configure it ready for kernel
2.4.9. However I get this output:
[root@fuse 1.0.1-rc2]# ./configure
.
. (omitted)
.
checking for st_rdev in struct stat... (cached) yes
checking whether time.h and sys/time.h may both be included... (cached) yes
./scripts/linuxver: [: ==: binary operator expected
./configure: [: ==: binary operator expected
checking whether gcc needs -traditional... (cached) no
checking return type of signal handlers... (cached) int
checking for vprintf... (cached) yes
checking for mkdir... (cached) yes
checking for rmdir... (cached) yes
checking for uname... (cached) yes
creating ./config.status
creating Makefile
creating make.tmpl
creating PATCHES/Makefile
creating tools/Makefile
creating tools/tools_and_lib.make.tmpl
creating tools/lib/Makefile
creating tools/man8/Makefile
./configure: ${srcdir/#\/*}: bad substitution
The patch seems to build OK however.
Another question - what kernel / lvm version do people recommend I use if I want
to avoid the MM problems in 2.4.9? I'd rather use a cutting edge version, but
what's the most stable? I couldn't seem to get 2.4.9-ac9 working, as it already
seems to have LVM beta7 parts in it and the patch doesn't work.
Has anyone had LVM 1.0.1-rc2 working with 2.4.10-pre12 ?
Regards,
James
next prev parent reply other threads:[~2001-09-20 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 16:06 [linux-lvm] Unresolved symbols in lvm-mod.o Brian Bailey
2001-09-20 7:31 ` Patrick Caulfield
2001-09-20 14:51 ` James Pattinson [this message]
2001-09-20 16:03 ` [linux-lvm] 1.0.1-rc2 config & kernel question AJ Lewis
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=1000997517.3baa028d1105c@mail.foobarhouse.com \
--to=jamesp@foobarhouse.com \
--cc=linux-lvm@sistina.com \
/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