Linux LVM users
 help / color / mirror / Atom feed
From: Glenn Shannon <warl0k@lvcm.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] troubled Guiness
Date: Sun, 26 Aug 2001 15:16:50 -0700	[thread overview]
Message-ID: <3B897552.8090400@lvcm.com> (raw)
In-Reply-To: 000e01c12e77$3382ca80$0300000a@pacbell.net

Erick Calder wrote:

>Hi all,
>
>I'm running RH 7.0 (Guiness) with the 2.2.16-22 kernel and gcc-2.96-85 and
>have downloaded the Linus 2.4.9 stock kernel which I'm trying to make... I
>built the patch and applied it with no apparent problem but when I try to
>build the kernel I get the errors in the log below.
>
>has anyone been here before?
>
>1k thx - e
>
>make[2]: Leaving directory `/usr/src/linux/drivers/ide'
>make -C md
>make[2]: Entering directory `/usr/src/linux/drivers/md'
>make all_targets
>make[3]: Entering directory `/usr/src/linux/drivers/md'
>gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-tri
>graphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpre
>ferred-stack-boundary=2 -march=i586    -c -o lvm.o lvm.c
>lvm.c:2329:71: macro "min" requires 3 arguments, but only 2 given
>lvm.c:2343:59: macro "min" requires 3 arguments, but only 2 given
>lvm.c: In function `__extend_reduce':
>lvm.c:2329: `min' undeclared (first use in this function)
>lvm.c:2329: (Each undeclared identifier is reported only once
>lvm.c:2329: for each function it appears in.)
>lvm.c:2280: warning: `end' might be used uninitialized in this function
>lvm.c:2339: warning: `end' might be used uninitialized in this function
>make[3]: *** [lvm.o] Error 1
>make[3]: Leaving directory `/usr/src/linux/drivers/md'
>make[2]: *** [first_rule] Error 2
>make[2]: Leaving directory `/usr/src/linux/drivers/md'
>make[1]: *** [_subdir_md] Error 2
>make[1]: Leaving directory `/usr/src/linux/drivers'
>make: *** [_dir_drivers] Error 2
>
>-----Original Message-----
>From:	linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com] On
>Behalf Of gerry@dorfam.ca
>Sent:	Sunday, August 26, 2001 6:21 AM
>To:	linux-lvm@sistina.com
>Subject:	RE: [linux-lvm] Successful Upgrade to 1.0 with RH 7.1
>
>On Sat, 25 Aug 2001, Erick Calder wrote:
>
>>>started with a clean Redhat 2.4.3-12 kernel
>>>
>>I'm running a stock 7.0 version and downloaded the above-named kernel...
>>patch and compilation went ok but I can't seem to make modules... I get a
>>ton of errors... I realised that I needed to install the kernel-headers
>>
>for
>
>>this version but even after that I can't make the modules... I've seen a
>>
>lot
>
>>of other guys out there suffering with this but no solutions... I even
>>
>tried
>
>>changing the HOSTCC to "kgcc" in the Makefile but no dice.... so I'm
>>wondering what you did right... can you share?
>>
>>(sorry everyone else that isn't running RH)
>>
>Well, all I did was follow the install instructions that came with the LVM
>tarball to create the patch.  I didn't do anything special.  I wasn't able
>to successfully install the newly created patch until I replaced the
>kernel source with a fresh "clean" rpm.
>
>Are you running the 2.4 kernel or are you using 2.2?  That makes a big
>difference as you need to add the raw.io patch to the 2.2 kernel.  Also, I
>don't believe that the shipped RH kernel config enables LVM as a default.
>
>I still have the patch for 2.4.3-12.  However, I doubt it would work for a
>7.0 install since I'm using 7.1.
>
>
>Gerry
>--
>"The lyfe so short, the craft so long to learne"  Geoffrey Chaucer
>
>
>_______________________________________________
>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
>
>
>_______________________________________________
>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
>
Actually, I got this same problem with the 2.4.9 kernel...I fixed it by 
installing clean source and using lvm1.0-rc1 instead.

Hope this helps.

Glenn

  reply	other threads:[~2001-08-26 22:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-19 21:39 [linux-lvm] Successful Upgrade to 1.0 with RH 7.1 gerry
2001-08-20  9:37 ` Heinz J . Mauelshagen
2001-08-26  3:56 ` Erick Calder
2001-08-26 13:21   ` gerry
2001-08-26 21:36     ` [linux-lvm] troubled Guiness Erick Calder
2001-08-26 22:16       ` Glenn Shannon [this message]
2001-08-30 21:10         ` [linux-lvm] core dumps with rc1 Erick Calder
2001-08-27 14:29       ` [linux-lvm] troubled Guiness AJ Lewis
2001-08-27 19:17         ` [linux-lvm] troubled Guiness - no longer! Erick Calder
2001-08-27 19:44           ` AJ Lewis

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=3B897552.8090400@lvcm.com \
    --to=warl0k@lvcm.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