All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerald Schepens <schepens@shaw.ca>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Building lvm2 against 2.6.10...
Date: Sun, 30 Jan 2005 23:23:49 -0700	[thread overview]
Message-ID: <41FDCEF5.1010600@shaw.ca> (raw)
In-Reply-To: <20050130095955.GL21542@percy.comedia.it>

Luca Berra wrote:

> On Sun, Jan 30, 2005 at 01:48:07AM -0700, Gerald Schepens wrote:
>
>> The configure script fails for lvm2 with the following...
>>
>> checking linux/fs.h usability... no
>> checking linux/fs.h presence... no
>> checking for linux/fs.h... no
>> configure: error: bailing out
>>
>> There isn't much of use in the config.log.
>
> well, there should be something, maybe something referring to pgoff_t?
>
> check you have defined pgoff_t in /usr/include/linux/types.h
>

Actually, I just wasn't looking far enough up in the config.log. I found 
a few of the problems but I haven't been able to get the thing to 
compile. Here's the skinny:

- The asm directory doesn't exist in the linux-2.6.10 subdirectory. 
There are only asm-ppc, asm-x86_64, asm-i386, etc. So I made a symlink 
to the appropriate one in /usr/include.

- There is no header file that I could find anyway, called 
libdevmapper.h. I symlinked it to device-mapper.h.

- Now, there's some kind of problem with the definition of sector_t.

Probably all things that need to be addressed in the future with regard 
to 2.6.10... unless, based on the things I've said here, my machine 
sounds like I've got installation issues.

  reply	other threads:[~2005-01-31  6:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-30  8:48 [linux-lvm] Building lvm2 against 2.6.10 Gerald Schepens
2005-01-30  9:59 ` Luca Berra
2005-01-31  6:23   ` Gerald Schepens [this message]
2005-02-01  7:00     ` Luca Berra
2005-02-01  7:20       ` Gerald Schepens
2005-02-01  7:52         ` Luca Berra

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=41FDCEF5.1010600@shaw.ca \
    --to=schepens@shaw.ca \
    --cc=linux-lvm@redhat.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.