[linux-lvm] lvm 0.9 kernel build problems

[linux-lvm] lvm 0.9 kernel build problems

[Patrick Swartz]

Hello,

Could someone give me some hints to why I get the following error when
trying to build my kernel with the lvm 0.9patches.  This box started out as
a RH7.0 with all current RH updates, then installed the stock 2.4.0-test10
kernel with lvm built into the kernel.  This build worked.  I then applied
the two patches for 2.4.0-test10 and they applied cleanly.  I normally build
kernels using the following approach -- make dep clean bzImage modules
modules_install, then take care of lilo.  This error happens during the
bzImage stage.


lvm.c: In function `lvm_do_vg_extend':
lvm.c:2020: warning: implicit declaration of function
`lvm_do_create_proc_entry_
of_pv'
lvm.c: In function `lvm_do_create_proc_entry_of_lv':
lvm.c:3012: `pde' undeclared (first use in this function)
lvm.c:3012: (Each undeclared identifier is reported only once
lvm.c:3012: for each function it appears in.)
lvm.c: At top level:
lvm.c:3040: warning: type mismatch with previous implicit declaration
lvm.c:2020: warning: previous implicit declaration of
`lvm_do_create_proc_entry_
of_pv'
lvm.c:3040: warning: `lvm_do_create_proc_entry_of_pv' was previously
implicitly
declared to return `int'
lvm.c: In function `lvm_do_create_proc_entry_of_pv':
lvm.c:3046: `pde' undeclared (first use in this function)
lvm.c: At top level:
lvm.c:146: warning: `lvm_short_version' defined but not used
make[3]: *** [lvm.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
make[1]: *** [_subdir_md] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers'
make: *** [_dir_drivers] Error 2

Thanks for your help,

Patrick Swartz

Re: [linux-lvm] lvm 0.9 kernel build problems

[Jay Weber]

I had the same errors in past when compiling it on 2.2.18pre kernels.
I believe my problem was that my /usr/src/linux didn't point back to the
proper kernel source tree.  It was a while ago though, but I'm thinking
that solved it for me.  I believe one of the files included in lvm.c is a
<linux/*whatever*> and that didn't exist or have the proper struct or
such.

On Wed, 29 Nov 2000, Patrick Swartz wrote:

> Hello,
> 
> Could someone give me some hints to why I get the following error when
> trying to build my kernel with the lvm 0.9patches.  This box started out as
> a RH7.0 with all current RH updates, then installed the stock 2.4.0-test10
> kernel with lvm built into the kernel.  This build worked.  I then applied
> the two patches for 2.4.0-test10 and they applied cleanly.  I normally build
> kernels using the following approach -- make dep clean bzImage modules
> modules_install, then take care of lilo.  This error happens during the
> bzImage stage.
> 
> 
> lvm.c: In function `lvm_do_vg_extend':
> lvm.c:2020: warning: implicit declaration of function
> `lvm_do_create_proc_entry_
> of_pv'
> lvm.c: In function `lvm_do_create_proc_entry_of_lv':
> lvm.c:3012: `pde' undeclared (first use in this function)
> lvm.c:3012: (Each undeclared identifier is reported only once
> lvm.c:3012: for each function it appears in.)
> lvm.c: At top level:
> lvm.c:3040: warning: type mismatch with previous implicit declaration
> lvm.c:2020: warning: previous implicit declaration of
> `lvm_do_create_proc_entry_
> of_pv'
> lvm.c:3040: warning: `lvm_do_create_proc_entry_of_pv' was previously
> implicitly
> declared to return `int'
> lvm.c: In function `lvm_do_create_proc_entry_of_pv':
> lvm.c:3046: `pde' undeclared (first use in this function)
> lvm.c: At top level:
> lvm.c:146: warning: `lvm_short_version' defined but not used
> make[3]: *** [lvm.o] Error 1
> make[3]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
> make[1]: *** [_subdir_md] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers'
> make: *** [_dir_drivers] Error 2
> 
> Thanks for your help,
> 
> Patrick Swartz
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> 

RE: [linux-lvm] lvm 0.9 kernel build problems

[Patrick Swartz]

I have found a way around the problem I was having.  The first time I tried
to build the kernel I built lvm into the kernel, but I said "no" to the lvm
proc fs question.  This time I went ahead and said "yes" and everything
worked.
Now my question is having lvm report things to /proc will I notice any slow
downs?
Just courious.

Thanks for all of the hard work everyone is putting into lvm!!!!!!!

Patrick

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On
Behalf Of Jay Weber
Sent: Wednesday, November 29, 2000 9:42 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm 0.9 kernel build problems


I had the same errors in past when compiling it on 2.2.18pre kernels.
I believe my problem was that my /usr/src/linux didn't point back to the
proper kernel source tree.  It was a while ago though, but I'm thinking
that solved it for me.  I believe one of the files included in lvm.c is a
<linux/*whatever*> and that didn't exist or have the proper struct or
such.

On Wed, 29 Nov 2000, Patrick Swartz wrote:

> Hello,
>
> Could someone give me some hints to why I get the following error when
> trying to build my kernel with the lvm 0.9patches.  This box started out
as
> a RH7.0 with all current RH updates, then installed the stock 2.4.0-test10
> kernel with lvm built into the kernel.  This build worked.  I then applied
> the two patches for 2.4.0-test10 and they applied cleanly.  I normally
build
> kernels using the following approach -- make dep clean bzImage modules
> modules_install, then take care of lilo.  This error happens during the
> bzImage stage.
>
>
> lvm.c: In function `lvm_do_vg_extend':
> lvm.c:2020: warning: implicit declaration of function
> `lvm_do_create_proc_entry_
> of_pv'
> lvm.c: In function `lvm_do_create_proc_entry_of_lv':
> lvm.c:3012: `pde' undeclared (first use in this function)
> lvm.c:3012: (Each undeclared identifier is reported only once
> lvm.c:3012: for each function it appears in.)
> lvm.c: At top level:
> lvm.c:3040: warning: type mismatch with previous implicit declaration
> lvm.c:2020: warning: previous implicit declaration of
> `lvm_do_create_proc_entry_
> of_pv'
> lvm.c:3040: warning: `lvm_do_create_proc_entry_of_pv' was previously
> implicitly
> declared to return `int'
> lvm.c: In function `lvm_do_create_proc_entry_of_pv':
> lvm.c:3046: `pde' undeclared (first use in this function)
> lvm.c: At top level:
> lvm.c:146: warning: `lvm_short_version' defined but not used
> make[3]: *** [lvm.o] Error 1
> make[3]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
> make[1]: *** [_subdir_md] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers'
> make: *** [_dir_drivers] Error 2
>
> Thanks for your help,
>
> Patrick Swartz
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
>

_______________________________________________
linux-lvm mailing list
linux-lvm@sistina.com
http://lists.sistina.com/mailman/listinfo/linux-lvm

RE: [linux-lvm] lvm 0.9 kernel build problems

[Jay Weber]

Ah thats' it.  Now my brain kicks in since you mentioned it.  That failure
from earlier only happens when you don't enable LVM proc-fs option.  I
guess it's a bug.  That's what I had todo.

On Wed, 29 Nov 2000, Patrick Swartz wrote:

> I have found a way around the problem I was having.  The first time I tried
> to build the kernel I built lvm into the kernel, but I said "no" to the lvm
> proc fs question.  This time I went ahead and said "yes" and everything
> worked.
> Now my question is having lvm report things to /proc will I notice any slow
> downs?
> Just courious.
> 
> Thanks for all of the hard work everyone is putting into lvm!!!!!!!
> 
> Patrick
> 
> -----Original Message-----
> From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On
> Behalf Of Jay Weber
> Sent: Wednesday, November 29, 2000 9:42 AM
> To: linux-lvm@sistina.com
> Subject: Re: [linux-lvm] lvm 0.9 kernel build problems
> 
> 
> I had the same errors in past when compiling it on 2.2.18pre kernels.
> I believe my problem was that my /usr/src/linux didn't point back to the
> proper kernel source tree.  It was a while ago though, but I'm thinking
> that solved it for me.  I believe one of the files included in lvm.c is a
> <linux/*whatever*> and that didn't exist or have the proper struct or
> such.
> 
> On Wed, 29 Nov 2000, Patrick Swartz wrote:
> 
> > Hello,
> >
> > Could someone give me some hints to why I get the following error when
> > trying to build my kernel with the lvm 0.9patches.  This box started out
> as
> > a RH7.0 with all current RH updates, then installed the stock 2.4.0-test10
> > kernel with lvm built into the kernel.  This build worked.  I then applied
> > the two patches for 2.4.0-test10 and they applied cleanly.  I normally
> build
> > kernels using the following approach -- make dep clean bzImage modules
> > modules_install, then take care of lilo.  This error happens during the
> > bzImage stage.
> >
> >
> > lvm.c: In function `lvm_do_vg_extend':
> > lvm.c:2020: warning: implicit declaration of function
> > `lvm_do_create_proc_entry_
> > of_pv'
> > lvm.c: In function `lvm_do_create_proc_entry_of_lv':
> > lvm.c:3012: `pde' undeclared (first use in this function)
> > lvm.c:3012: (Each undeclared identifier is reported only once
> > lvm.c:3012: for each function it appears in.)
> > lvm.c: At top level:
> > lvm.c:3040: warning: type mismatch with previous implicit declaration
> > lvm.c:2020: warning: previous implicit declaration of
> > `lvm_do_create_proc_entry_
> > of_pv'
> > lvm.c:3040: warning: `lvm_do_create_proc_entry_of_pv' was previously
> > implicitly
> > declared to return `int'
> > lvm.c: In function `lvm_do_create_proc_entry_of_pv':
> > lvm.c:3046: `pde' undeclared (first use in this function)
> > lvm.c: At top level:
> > lvm.c:146: warning: `lvm_short_version' defined but not used
> > make[3]: *** [lvm.o] Error 1
> > make[3]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
> > make[2]: *** [first_rule] Error 2
> > make[2]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
> > make[1]: *** [_subdir_md] Error 2
> > make[1]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers'
> > make: *** [_dir_drivers] Error 2
> >
> > Thanks for your help,
> >
> > Patrick Swartz
> >
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> >
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> 

Re: [linux-lvm] lvm 0.9 kernel build problems

[Heinz J. Mauelshagen]

On Wed, Nov 29, 2000 at 11:19:46AM -0600, Patrick Swartz wrote:
> I have found a way around the problem I was having.  The first time I tried
> to build the kernel I built lvm into the kernel, but I said "no" to the lvm
> proc fs question.  This time I went ahead and said "yes" and everything
> worked.

I think I already fixed that bug.
It will be available with 0.9.1

> Now my question is having lvm report things to /proc will I notice any slow
> downs?

No.

Only if you read from LVM's /proc interface there's _very_ little load on
the driver.

> Just courious.
> 
> Thanks for all of the hard work everyone is putting into lvm!!!!!!!
> 
> Patrick
> 
> -----Original Message-----
> From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On
> Behalf Of Jay Weber
> Sent: Wednesday, November 29, 2000 9:42 AM
> To: linux-lvm@sistina.com
> Subject: Re: [linux-lvm] lvm 0.9 kernel build problems
> 
> 
> I had the same errors in past when compiling it on 2.2.18pre kernels.
> I believe my problem was that my /usr/src/linux didn't point back to the
> proper kernel source tree.  It was a while ago though, but I'm thinking
> that solved it for me.  I believe one of the files included in lvm.c is a
> <linux/*whatever*> and that didn't exist or have the proper struct or
> such.
> 
> On Wed, 29 Nov 2000, Patrick Swartz wrote:
> 
> > Hello,
> >
> > Could someone give me some hints to why I get the following error when
> > trying to build my kernel with the lvm 0.9patches.  This box started out
> as
> > a RH7.0 with all current RH updates, then installed the stock 2.4.0-test10
> > kernel with lvm built into the kernel.  This build worked.  I then applied
> > the two patches for 2.4.0-test10 and they applied cleanly.  I normally
> build
> > kernels using the following approach -- make dep clean bzImage modules
> > modules_install, then take care of lilo.  This error happens during the
> > bzImage stage.
> >
> >
> > lvm.c: In function `lvm_do_vg_extend':
> > lvm.c:2020: warning: implicit declaration of function
> > `lvm_do_create_proc_entry_
> > of_pv'
> > lvm.c: In function `lvm_do_create_proc_entry_of_lv':
> > lvm.c:3012: `pde' undeclared (first use in this function)
> > lvm.c:3012: (Each undeclared identifier is reported only once
> > lvm.c:3012: for each function it appears in.)
> > lvm.c: At top level:
> > lvm.c:3040: warning: type mismatch with previous implicit declaration
> > lvm.c:2020: warning: previous implicit declaration of
> > `lvm_do_create_proc_entry_
> > of_pv'
> > lvm.c:3040: warning: `lvm_do_create_proc_entry_of_pv' was previously
> > implicitly
> > declared to return `int'
> > lvm.c: In function `lvm_do_create_proc_entry_of_pv':
> > lvm.c:3046: `pde' undeclared (first use in this function)
> > lvm.c: At top level:
> > lvm.c:146: warning: `lvm_short_version' defined but not used
> > make[3]: *** [lvm.o] Error 1
> > make[3]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
> > make[2]: *** [first_rule] Error 2
> > make[2]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
> > make[1]: *** [_subdir_md] Error 2
> > make[1]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers'
> > make: *** [_dir_drivers] Error 2
> >
> > Thanks for your help,
> >
> > Patrick Swartz
> >
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> >
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm

-- 

Regards,
Heinz      -- The LVM guy --

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Bartningstr. 12
                                                  64289 Darmstadt
                                                  Germany
Mauelshagen@Sistina.com                           +49 6151 7103 86
                                                       FAX 7103 96
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-lvm] lvm 0.9 kernel build problems

[Heinz J. Mauelshagen]

I guess that this could be a nasty gcc flaw showing up here.

Anybody else who tried to patch/compile LVM 0.9 with linux-2.4.0-test10
on RH 7.0 who is able to help?


On Wed, Nov 29, 2000 at 09:05:32AM -0600, Patrick Swartz wrote:
> Hello,
> 
> Could someone give me some hints to why I get the following error when
> trying to build my kernel with the lvm 0.9patches.  This box started out as
> a RH7.0 with all current RH updates, then installed the stock 2.4.0-test10
> kernel with lvm built into the kernel.  This build worked.  I then applied
> the two patches for 2.4.0-test10 and they applied cleanly.  I normally build
> kernels using the following approach -- make dep clean bzImage modules
> modules_install, then take care of lilo.  This error happens during the
> bzImage stage.
> 
> 
> lvm.c: In function `lvm_do_vg_extend':
> lvm.c:2020: warning: implicit declaration of function
> `lvm_do_create_proc_entry_
> of_pv'
> lvm.c: In function `lvm_do_create_proc_entry_of_lv':
> lvm.c:3012: `pde' undeclared (first use in this function)
> lvm.c:3012: (Each undeclared identifier is reported only once
> lvm.c:3012: for each function it appears in.)
> lvm.c: At top level:
> lvm.c:3040: warning: type mismatch with previous implicit declaration
> lvm.c:2020: warning: previous implicit declaration of
> `lvm_do_create_proc_entry_
> of_pv'
> lvm.c:3040: warning: `lvm_do_create_proc_entry_of_pv' was previously
> implicitly
> declared to return `int'
> lvm.c: In function `lvm_do_create_proc_entry_of_pv':
> lvm.c:3046: `pde' undeclared (first use in this function)
> lvm.c: At top level:
> lvm.c:146: warning: `lvm_short_version' defined but not used
> make[3]: *** [lvm.o] Error 1
> make[3]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
> make[1]: *** [_subdir_md] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers'
> make: *** [_dir_drivers] Error 2
> 
> Thanks for your help,
> 
> Patrick Swartz
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm

-- 

Regards,
Heinz      -- The LVM guy --

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Bartningstr. 12
                                                  64289 Darmstadt
                                                  Germany
Mauelshagen@Sistina.com                           +49 6151 7103 86
                                                       FAX 7103 96
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-lvm] lvm 0.9 kernel build problems

[Falcon]

You must to change gcc by kgcc in the Makefile
----- Original Message -----
From: "Heinz J. Mauelshagen" <Heinz.Mauelshagen@t-online.de>
To: <linux-lvm@sistina.com>
Cc: <mge@sistina.com>
Sent: Wednesday, November 29, 2000 10:19 PM
Subject: Re: [linux-lvm] lvm 0.9 kernel build problems


>
> I guess that this could be a nasty gcc flaw showing up here.
>
> Anybody else who tried to patch/compile LVM 0.9 with linux-2.4.0-test10
> on RH 7.0 who is able to help?
>
>
> On Wed, Nov 29, 2000 at 09:05:32AM -0600, Patrick Swartz wrote:
> > Hello,
> >
> > Could someone give me some hints to why I get the following error when
> > trying to build my kernel with the lvm 0.9patches.  This box started out
as
> > a RH7.0 with all current RH updates, then installed the stock
2.4.0-test10
> > kernel with lvm built into the kernel.  This build worked.  I then
applied
> > the two patches for 2.4.0-test10 and they applied cleanly.  I normally
build
> > kernels using the following approach -- make dep clean bzImage modules
> > modules_install, then take care of lilo.  This error happens during the
> > bzImage stage.
> >
> >
> > lvm.c: In function `lvm_do_vg_extend':
> > lvm.c:2020: warning: implicit declaration of function
> > `lvm_do_create_proc_entry_
> > of_pv'
> > lvm.c: In function `lvm_do_create_proc_entry_of_lv':
> > lvm.c:3012: `pde' undeclared (first use in this function)
> > lvm.c:3012: (Each undeclared identifier is reported only once
> > lvm.c:3012: for each function it appears in.)
> > lvm.c: At top level:
> > lvm.c:3040: warning: type mismatch with previous implicit declaration
> > lvm.c:2020: warning: previous implicit declaration of
> > `lvm_do_create_proc_entry_
> > of_pv'
> > lvm.c:3040: warning: `lvm_do_create_proc_entry_of_pv' was previously
> > implicitly
> > declared to return `int'
> > lvm.c: In function `lvm_do_create_proc_entry_of_pv':
> > lvm.c:3046: `pde' undeclared (first use in this function)
> > lvm.c: At top level:
> > lvm.c:146: warning: `lvm_short_version' defined but not used
> > make[3]: *** [lvm.o] Error 1
> > make[3]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
> > make[2]: *** [first_rule] Error 2
> > make[2]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
> > make[1]: *** [_subdir_md] Error 2
> > make[1]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers'
> > make: *** [_dir_drivers] Error 2
> >
> > Thanks for your help,
> >
> > Patrick Swartz
> >
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
>
> --
>
> Regards,
> Heinz      -- The LVM guy --
>
>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
=-
>
> Heinz Mauelshagen                                 Sistina Software Inc.
> Senior Consultant/Developer                       Bartningstr. 12
>                                                   64289 Darmstadt
>                                                   Germany
> Mauelshagen@Sistina.com                           +49 6151 7103 86
>                                                        FAX 7103 96
>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
=-
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: [linux-lvm] lvm 0.9 kernel build problems

[Chewie]

[-- Attachment #1: Type: text/plain, Size: 592 bytes --]

On Wed, Nov 29, 2000 at 10:47:09PM +0100, Falcon wrote:
> You must to change gcc by kgcc in the Makefile

<rant>
Is it just me, or does this sound like a Red Hat-like solution?  Gee.
Let's package an old version of gcc just so we can compile the kernel
correctly.  We can't simply use a stable gcc as our standard compiler.
We have to reach back into the bag of the ancients to keep our
machines running and make it LOOK like we're using the bleeding edge
with gcc 2.96!
</rant>

-- 
Chad "^chewie, gunnarr" Walstrom <chewie@wookimus.net>
             http://www.wookimus.net/

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [linux-lvm] lvm 0.9 kernel build problems

[Stephen C. Tweedie]

Hi,

On Thu, Nov 30, 2000 at 02:44:49AM -0600, Chewie wrote:
> On Wed, Nov 29, 2000 at 10:47:09PM +0100, Falcon wrote:
> > You must to change gcc by kgcc in the Makefile
> 
> <rant>
> Is it just me, or does this sound like a Red Hat-like solution?  Gee.
> Let's package an old version of gcc just so we can compile the kernel
> correctly.  We can't simply use a stable gcc as our standard compiler.

Good grief.  Is it just me, or has this thread been beaten to death
already on linux-kernel?

Connectiva, Red Hat, Debian and (I think) Mandrake are all shipping an
older compiler for the kernel now, simply because too many things in
the kernel are fragile and break if the compiler reorders instructions
in an unexpected way.

The fault here is actually the kernel's: if the kernel doesn't specify
its ordering constraints explicitly enough, then change the kernel and
you can break silent assumptions that the kernel was making, causing
obscure and hard-to-diagnose errors on SMP machines or when code is
interrupted.

This is nothing new --- since forever, there have been specific
compilers known to work with specific kernel versions, and using a
different compiler (older OR newer) has been likely to break things.  

--Stephen

Re: [linux-lvm] lvm 0.9 kernel build problems

[Eric M. Hopper]

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]

On Thu, Nov 30, 2000 at 02:44:49AM -0600, Chewie wrote:
> On Wed, Nov 29, 2000 at 10:47:09PM +0100, Falcon wrote:
> > You must to change gcc by kgcc in the Makefile
> 
> <rant>
> Is it just me, or does this sound like a Red Hat-like solution?  Gee.
> Let's package an old version of gcc just so we can compile the kernel
> correctly.  We can't simply use a stable gcc as our standard compiler.
> We have to reach back into the bag of the ancients to keep our
> machines running and make it LOOK like we're using the bleeding edge
> with gcc 2.96!
> </rant>

	If I'm not mistaken, the reasons the new gcc won't compile the
kernel have more to do with the kernel than with the new gcc.  This
problem has happened several times in the past, and it was usually (with
one notable exception in gcc 2.7.1) the kernel's fault.

Have fun (if at all possible),
-- 
The best we can hope for concerning the people at large is that they
be properly armed.  -- Alexander Hamilton
-- Eric Hopper (hopper@omnifarious.mn.org http://www.omnifarious.org/~hopper) --

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [linux-lvm] lvm 0.9 kernel build problems

[Rik van Riel]

On Thu, 30 Nov 2000, Chewie wrote:
> On Wed, Nov 29, 2000 at 10:47:09PM +0100, Falcon wrote:
> > You must to change gcc by kgcc in the Makefile
> 
> <rant>
> Is it just me, or does this sound like a Red Hat-like solution?  Gee.

It's just you, don't worry.

cheers,

Rik
--
Hollywood goes for world dumbination,
	Trailer at 11.

		http://www.surriel.com/
http://www.conectiva.com/	http://distro.conectiva.com.br/

OT: Re: [linux-lvm] lvm 0.9 kernel build problems

[Chewie]

[-- Attachment #1: Type: text/plain, Size: 626 bytes --]

{ Modified for the sake of brevity }
Falcon> You must to change gcc by kgcc in the Makefile
Chewie> <rant> Is it just me, or does this sound like a Red
        Hat-like solution?  Gee. 
Rik>    It's just you, don't worry.

I find it odd then, that I've had no problems compiling stock and
patched kernels with 3.95.2 that weren't my own fault.  Anyway, I'll
take this off list as its leaning toward being off topic and as it was
said earlier, this topic's been beaten to death on lkml.  Sorry for
bringing it up.

-- 
Chad "^chewie, gunnarr" Walstrom <chewie@wookimus.net>
             http://www.wookimus.net/

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [linux-lvm] lvm 0.9 kernel build problems

[Steven Lembark]

> I guess that this could be a nasty gcc flaw showing up here.
> 
> Anybody else who tried to patch/compile LVM 0.9 with linux-2.4.0-test10
> on RH 7.0 who is able to help?
> <snip>

tried, failed, gave up...

if anyone who knows more about what problems to expect wants
to take a shot at it i can put a copy of the 7.0 respin *
& 0.9 on a machine here and give you a login to try it out.

-- 
 Steven Lembark                                   2930 W. Palmer St.
                                                 Chicago, IL  60647
 lembark@wrkhors.com                                   800-762-1582

Re: [linux-lvm] lvm 0.9 kernel build problems

[Heinz J. Mauelshagen]

Somebody figured that one out already.

It is a bug which shows up in case you deselect LVM proc filesystem support.

Please enable it for now and you should be able to compile quite happily.

On Wed, Nov 29, 2000 at 09:05:32AM -0600, Patrick Swartz wrote:
> Hello,
> 
> Could someone give me some hints to why I get the following error when
> trying to build my kernel with the lvm 0.9patches.  This box started out as
> a RH7.0 with all current RH updates, then installed the stock 2.4.0-test10
> kernel with lvm built into the kernel.  This build worked.  I then applied
> the two patches for 2.4.0-test10 and they applied cleanly.  I normally build
> kernels using the following approach -- make dep clean bzImage modules
> modules_install, then take care of lilo.  This error happens during the
> bzImage stage.
> 
> 
> lvm.c: In function `lvm_do_vg_extend':
> lvm.c:2020: warning: implicit declaration of function
> `lvm_do_create_proc_entry_
> of_pv'
> lvm.c: In function `lvm_do_create_proc_entry_of_lv':
> lvm.c:3012: `pde' undeclared (first use in this function)
> lvm.c:3012: (Each undeclared identifier is reported only once
> lvm.c:3012: for each function it appears in.)
> lvm.c: At top level:
> lvm.c:3040: warning: type mismatch with previous implicit declaration
> lvm.c:2020: warning: previous implicit declaration of
> `lvm_do_create_proc_entry_
> of_pv'
> lvm.c:3040: warning: `lvm_do_create_proc_entry_of_pv' was previously
> implicitly
> declared to return `int'
> lvm.c: In function `lvm_do_create_proc_entry_of_pv':
> lvm.c:3046: `pde' undeclared (first use in this function)
> lvm.c: At top level:
> lvm.c:146: warning: `lvm_short_version' defined but not used
> make[3]: *** [lvm.o] Error 1
> make[3]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers/md'
> make[1]: *** [_subdir_md] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.0-test10/drivers'
> make: *** [_dir_drivers] Error 2
> 
> Thanks for your help,
> 
> Patrick Swartz
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm

-- 

Regards,
Heinz      -- The LVM guy --

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Bartningstr. 12
                                                  64289 Darmstadt
                                                  Germany
Mauelshagen@Sistina.com                           +49 6151 7103 86
                                                       FAX 7103 96
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-