Linux LVM users
 help / color / mirror / Atom feed
From: Klaus Strebel <stb@ep-ag.com>
To: lars@larsshack.org
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] Building lvm tools? (fwd)
Date: Tue, 08 Feb 2000 09:23:03 +0100	[thread overview]
Message-ID: <389FD267.FD41DA95@ep-ag.com> (raw)
In-Reply-To: 389F6445.218E6DD7@msede.com

Hi Lars,

> Howdy,
> 
> I'm trying to build the lvm under RedHat 6.1 (linux 2.2.14 + devfs),
...
> I'm using the 0.8-pre02.10.1999 release of the tools.
> 
> After typing 'make', the build dies with errors along these lines:
> 
>   cc -c -pipe -Wall -I/usr/src/LVM/0.8-pre02.10.1999/tools
> -I/usr/src/LVM/0.8-pre0
>   2.10.1999/tools/lib -I/usr/src/LVM/0.8-pre02.10.1999/kernel
> -D__KERNEL__ -O2 -DD
>   EBUG -o debug.o debug.c
>   In file included from /usr/include/linux/fs.h:20,
>                    from /usr/include/linux/devfs_fs_kernel.h:4,
>                    from /usr/include/linux/genhd.h:14,
>                    from /usr/src/LVM/0.8-pre02.10.1999/tools/lib/liblvm.h:103,
>                    from basename.c:26:
>   /usr/include/linux/stat.h:12: warning: `S_IFMT' redefined
>   /usr/include/sys/stat.h:92: warning: this is the location of the
> previous defini
>   tion
>   /usr/include/linux/stat.h:13: warning: `S_IFSOCK' redefined
>   /usr/include/sys/stat.h:105: warning: this is the location of the
> previous defin
>   ition
>   [...ad nauseum...]
> 
> These errors occur for virtually every file in the distribution.  Has
> anyone else encountered this problem?
well, the devfs includes seem to depend on __KERNEL__ things, it solved
it on my box with the following hack (houuu, real ugly ;-)):

First, remove the -D__KERNEL__ from the Makefiles (of the lvm-tools of
cause!), then add this to $(KERN_SOURCES)/include/linux/lvm.h around the
include of linux/kdev_t.h (about line 90 or so):

/* KS : Look out! Following is a bad, bad hack solving compile problems
for tools! */
#if !defined (__KERNEL__)
#define  __KERNEL__ 1
#include <linux/kdev_t.h>
#undef __KERNEL__
#else
#include <linux/kdev_t.h>
#endif
#include <linux/major.h>
#include <asm/spinlock.h>

Works for, hope the same for you.

Bye
Klaus
-- 
Klaus Strebel
stb@ep-ag.com
EIGNER + PARTNER AG   - The Engineering Warehouse Company -
<http://www.ep-ag.com>
-----------------------------------------------------------------------

      reply	other threads:[~2000-02-08  8:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-08  0:33 [linux-lvm] Building lvm tools? (fwd) Michael Marxmeier
2000-02-08  8:23 ` Klaus Strebel [this message]

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=389FD267.FD41DA95@ep-ag.com \
    --to=stb@ep-ag.com \
    --cc=lars@larsshack.org \
    --cc=linux-lvm@msede.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