From: Luca Berra <bluca@comedia.it>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Building lvm2 against 2.6.10...
Date: Sun, 30 Jan 2005 10:59:55 +0100 [thread overview]
Message-ID: <20050130095955.GL21542@percy.comedia.it> (raw)
In-Reply-To: <41FC9F47.4030001@shaw.ca>
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
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2005-01-30 10:00 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 [this message]
2005-01-31 6:23 ` Gerald Schepens
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=20050130095955.GL21542@percy.comedia.it \
--to=bluca@comedia.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox