From: Jeff Layton <jeffrey.b.layton@lmco.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Building LVM ona RH7.2 - errors
Date: Wed Feb 13 04:52:01 2002 [thread overview]
Message-ID: <3C6A45BD.E4534C36@lmco.com> (raw)
In-Reply-To: 20020213095631.GD1028@tykepenguin.com
Patrick Caulfield wrote:
> On Tue, Feb 12, 2002 at 06:47:38PM -0500, Jeff Layton wrote:
> > Good evening,
> >
> > I tried building lvm-1.0.2 against a clean 2.4.17
> > kernel. I untarred the lvm tar.gz file as well as
> > the 2.4.17 kernel (into /usr/src/linux-2.4.17.clean).
> > Then I did a,
> >
> > ./configure --with-kernel_dir=/usr/src/linux-2.4.17.clean
> >
> > from /usr/src/LVLM/1.0.2 I get the following errors
> > during the configure process,
>
> >
> > checking whether time.h and sys/time.h may both be included... yes
> > ./configure: [: too many arguments
> > checking whether gcc needs -traditional... no
>
> >
> > (sorry about the length). sed is not my string point at all.
> > Any ideas what I'm doing wrong?
> >
>
> It looks like there's something funny with your kernel sources, maybe a space in
> the version number perhaps - check the Makefile.
>
> I just tried a kernel.org kernel and 1.0.2 on RH 7.2 here and it's fine.
I'll try it again, but the kernel source was pristine. I untarred it
to /usr/src/linux and mv'ed it to /usr/src/linux-2.4.17.clean.
Thanks
Jeff
>
>
> patrick
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
next prev parent reply other threads:[~2002-02-13 4:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 17:46 [linux-lvm] Building LVM ona RH7.2 - errors Jeff Layton
2002-02-13 3:56 ` Patrick Caulfield
2002-02-13 4:52 ` Jeff Layton [this message]
2002-02-14 1:21 ` Luca Berra
2002-02-14 16:58 ` Jeff Layton
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=3C6A45BD.E4534C36@lmco.com \
--to=jeffrey.b.layton@lmco.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 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.