From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problem at compiling kernel 2.4.18 with lvm 1.0.7
Date: Thu Oct 30 04:24:01 2003 [thread overview]
Message-ID: <20031030112411.A1850@sistina.com> (raw)
In-Reply-To: <55752b312642ea42b36cdcbd85025670@10.3.11.254>; from krisztian.gyoerffy@selecktra.com on Wed, Oct 29, 2003 at 01:19:26PM +0100
Krisztian,
running the SuSE LVM rpm with the SuSE kernel should work fine.
Have you tried that yet ?
Regards,
Heinz -- The LVM Guy --
On Wed, Oct 29, 2003 at 01:19:26PM +0100, Krisztian Gyoerffy wrote:
> Hi LVM friends,
>
>
> I have problems with the following scenario:
>
> - I use SuSE linux 7.1 (I know, this might be a bit old, but I follow
> the rule "never touch a running system") with kernel 2.4.16 and lvm
> 1.0.7
>
> - Since SuSE rolled out the latest kernel for 7.1 and I would like to
> keep my OS up to date I installed the 2.4.18 kernel source from SuSE on
> my machine
>
> - I tried to patch the kernel with the LVM 1.0.7, so I executed exactly
> the steps written in INSTALL and PATCH/README. Everything was ok
>
> - Then I configured the rest of the kernel and tried to compile. But
> after a while, when it was compiling the LVM stuff, it stopped compiling
> with the following message:
>
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.18.SuSE/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686
> -DKBUILD_BASENAME=lvm -c -o lvm.o lvm.c
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.18.SuSE/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686
> -DKBUILD_BASENAME=lvm_snap -c -o lvm-snap.o lvm-snap.c
> lvm-snap.c: In function `lvm_snapshot_COW':
> lvm-snap.c:365: structure has no member named `blocks'
> make[3]: *** [lvm-snap.o] Error 1
> make[3]: Leaving directory
> `/usr/src/linux-2.4.18.SuSE/drivers/md'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory
> `/usr/src/linux-2.4.18.SuSE/drivers/md'
> make[1]: *** [_subdir_md] Error 2
> make[1]: Leaving directory
> `/usr/src/linux-2.4.18.SuSE/drivers'
> make: *** [_dir_drivers] Error 2
>
> Afterwards I looked into the patch file, and into the lvm-snap.c at the
> given position, line 365. There is the reference to the "blocks"
> variable of the iobuf structure. This iobuf structure is defined in the
> /usr/src/linux/include/linux/iobuf.h header file. But this header file
> is completly different in the source of the 2.4.18 kernel than in the
> source of the 2.4.16 kernel, where the patch and compiling were ok.
>
> Do you have any idea what can I do to get it compiled?
>
> I attach the lvm patch file generated by make and the iobuf.h file for
> both versions 2.4.16 and 2.4.18.
>
>
> Hope to hear from you soon, and thanks in advance
>
>
> Krisztian
>
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2003-10-30 4:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 8:54 [linux-lvm] Problem at compiling kernel 2.4.18 with lvm 1.0.7 Krisztian Gyoerffy
2003-10-30 4:24 ` Heinz J . Mauelshagen [this message]
2003-10-30 5:00 ` Krisztian Gyoerffy
2003-10-31 4:28 ` Heinz J . Mauelshagen
2003-10-31 6:55 ` Krisztian Gyoerffy
2003-10-31 8:32 ` Heinz J . Mauelshagen
-- strict thread matches above, loose matches on Subject: below --
2003-10-29 8:54 Krisztian Gyoerffy
2003-10-29 8:54 Krisztian Gyoerffy
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=20031030112411.A1850@sistina.com \
--to=mauelshagen@sistina.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