Re: compiler errors: md needed for hardware raid?
On Wed, Jul 16, 2003 at 12:18:31PM +0200, Lars Oeschey wrote: > Am Dienstag, 15. Juli 2003 16:37 schrieb Patrick Caulfield: > > > LVM works fine on Alpha, though personally I'm using LVM2 now :-) > > Yes it wil do RAID0 without md. if you want RAID1 or RAID5 then you > > need to set up md and /then/ LVM > > hm, I just wanted to remove md support from the kernel, but that > deactivates LVM also... > In xconfig it's under the option "Multi device support (Raid and LVM)", > and when I remove the "Multiple devices driver support (RAID and LVM)", > the option "LVM support" gets greyed out... That's right "Multiple devices driver support (RAID and LVM)" is just a general thing that covers md and LVM1, there's no actual code involved. To disable md simply don't select any of the RAID options on that menu. The options are only grouped together cos they do similar things, not because they share code. -- patrick
Re: compiler errors: md needed for hardware raid?
Am Dienstag, 15. Juli 2003 16:37 schrieb Patrick Caulfield: > LVM works fine on Alpha, though personally I'm using LVM2 now :-) > Yes it wil do RAID0 without md. if you want RAID1 or RAID5 then you > need to set up md and /then/ LVM hm, I just wanted to remove md support from the kernel, but that deactivates LVM also... In xconfig it's under the option "Multi device support (Raid and LVM)", and when I remove the "Multiple devices driver support (RAID and LVM)", the option "LVM support" gets greyed out... Lars
Re: compiler errors: md needed for hardware raid?
Am Dienstag, 15. Juli 2003 16:37 schrieb Patrick Caulfield: > > I think LVM2 can do at least raid0 on its own. I don't know whether > > it is well-tested on Alpha, though, I've never used it :) > LVM works fine on Alpha, though personally I'm using LVM2 now :-) > Yes it wil do RAID0 without md. if you want RAID1 or RAID5 then you > need to set up md and /then/ LVM ok, I will leave md out then... Another thing, under /usr/src I have a directory kernel-patches with an executable inside. Do I need to apply those patches manually, or is it done by make-kpkg? Lars
Re: compiler errors: md needed for hardware raid?
On Tue, Jul 15, 2003 at 04:18:54PM +0200, Falk Hueffner wrote: > Lars Oeschey <[EMAIL PROTECTED]> writes: > > > Am Dienstag, 15. Juli 2003 15:19 schrieb Falk Hueffner: > > mh, ok... But I found that I need some kind of software raid, I have > > several partitions on external cabinets (that old mylex controllers > > support partitions only up to 32Gb) and I want to combine those to one > > big drive. > > I took a look ant md and LVM now, but what I didn't find is, does LVM > > need md? or is it more of a replacement for it? > > Cause then I could just use LVM... > > I think LVM2 can do at least raid0 on its own. I don't know whether it > is well-tested on Alpha, though, I've never used it :) LVM works fine on Alpha, though personally I'm using LVM2 now :-) Yes it wil do RAID0 without md. if you want RAID1 or RAID5 then you need to set up md and /then/ LVM -- patrick
Re: compiler errors: md needed for hardware raid?
Lars Oeschey <[EMAIL PROTECTED]> writes: > Am Dienstag, 15. Juli 2003 15:19 schrieb Falk Hueffner: > mh, ok... But I found that I need some kind of software raid, I have > several partitions on external cabinets (that old mylex controllers > support partitions only up to 32Gb) and I want to combine those to one > big drive. > I took a look ant md and LVM now, but what I didn't find is, does LVM > need md? or is it more of a replacement for it? > Cause then I could just use LVM... I think LVM2 can do at least raid0 on its own. I don't know whether it is well-tested on Alpha, though, I've never used it :) -- Falk
Re: compiler errors: md needed for hardware raid?
Am Dienstag, 15. Juli 2003 15:19 schrieb Falk Hueffner: > Eek. That file uses multiline string literals, which is no longer > accepted by gcc. > You could just start each line within the asm argument with " and > finish with \n\t". uhoh... > Software. mh, ok... But I found that I need some kind of software raid, I have several partitions on external cabinets (that old mylex controllers support partitions only up to 32Gb) and I want to combine those to one big drive. I took a look ant md and LVM now, but what I didn't find is, does LVM need md? or is it more of a replacement for it? Cause then I could just use LVM... Lars
Re: compiler errors: md needed for hardware raid?
Am Dienstag, 15. Juli 2003 15:20 schrieb Ionut Georgescu: > What does gcc -v say ? You need gcc-3.x for the alpha. gcc version 3.3.1 20030626 (Debian prerelease) > PS apt-get remove cpp-2.95 will remove gcc 2.95.x and automatically > install gcc-3.x (in testing at least) yup, did that, because just installing 3.3 wouldn't make it active ;) Lars
Re: compiler errors: md needed for hardware raid?
What does gcc -v say ? You need gcc-3.x for the alpha. Ionut PS apt-get remove cpp-2.95 will remove gcc 2.95.x and automatically install gcc-3.x (in testing at least) On Tue, Jul 15, 2003 at 03:06:39PM +0200, Lars Oeschey wrote: > Hi, > > when trying to compile the 2.4.21 kernel I get compiler errors within > /drivers/md: > > make[4]: Entering directory `/usr/src/kernel-source-2.4.21/drivers/md' > gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.21/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common > -fomit-frame-pointer -pipe -mno-fp-regs -ffixed-8 -mcpu=ev5 -Wa,-mev6 > -nostdinc -iwithprefix include -DKBUILD_BASENAME=linear -c -o linear.o > linear.c > gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.21/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common > -fomit-frame-pointer -pipe -mno-fp-regs -ffixed-8 -mcpu=ev5 -Wa,-mev6 > -nostdinc -iwithprefix include -DKBUILD_BASENAME=raid0 -c -o raid0.o > raid0.c > gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.21/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common > -fomit-frame-pointer -pipe -mno-fp-regs -ffixed-8 -mcpu=ev5 -Wa,-mev6 > -nostdinc -iwithprefix include -DKBUILD_BASENAME=raid1 -c -o raid1.o > raid1.c > gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.21/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common > -fomit-frame-pointer -pipe -mno-fp-regs -ffixed-8 -mcpu=ev5 -Wa,-mev6 > -nostdinc -iwithprefix include -DKBUILD_BASENAME=raid5 -c -o raid5.o > raid5.c > gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.21/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common > -fomit-frame-pointer -pipe -mno-fp-regs -ffixed-8 -mcpu=ev5 -Wa,-mev6 > -nostdinc -iwithprefix include -DKBUILD_BASENAME=xor -DEXPORT_SYMTAB > -c xor.c > In file included from xor.c:23: > /usr/src/kernel-source-2.4.21/include/asm/xor.h:35:5: missing > terminating " character > In file included from xor.c:23: > /usr/src/kernel-source-2.4.21/include/asm/xor.h:36: error: request for > member `text' in something not a structure or union > /usr/src/kernel-source-2.4.21/include/asm/xor.h:37: error: syntax error > before numeric constant > /usr/src/kernel-source-2.4.21/include/asm/xor.h:62: error: syntax error > at '#' token > /usr/src/kernel-source-2.4.21/include/asm/xor.h:87:17: invalid suffix > "b" on integer constant > /usr/src/kernel-source-2.4.21/include/asm/xor.h:119: error: syntax error > at '#' token > /usr/src/kernel-source-2.4.21/include/asm/xor.h:120: error: syntax error > at '#' token > /usr/src/kernel-source-2.4.21/include/asm/xor.h:121: error: syntax error > at '#' token > /usr/src/kernel-source-2.4.21/include/asm/xor.h:122: error: syntax error > at '#' token > > > xor.c: In function `calibrate_xor_block': > xor.c:117: error: `xor_block_alpha' undeclared (first use in this > function) > xor.c:117: error: (Each undeclared identifier is reported only once > xor.c:117: error: for each function it appears in.) > make[4]: *** [xor.o] Error 1 > make[4]: Leaving directory `/usr/src/kernel-source-2.4.21/drivers/md' > make[3]: *** [first_rule] Error 2 > make[3]: Leaving directory `/usr/src/kernel-source-2.4.21/drivers/md' > make[2]: *** [_subdir_md] Error 2 > make[2]: Leaving directory `/usr/src/kernel-source-2.4.21/drivers' > make[1]: *** [_dir_drivers] Error 2 > make[1]: Leaving directory `/usr/src/kernel-source-2.4.21' > make: *** [stamp-build] Error 2 > > I couldn't find anything on this error at google, so my question is: is > the md driver needed for hardware raids or is it just for software > raids? So I could perhaps completely leave it out... > > Lars > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- *** * Ionut Georgescu * http://www.physik.tu-cottbus.de/~george/ * Registered Linux User #244479 * * "In Windows you can do everything Microsoft wants you to do; in Unix you *can do anything the computer is able to do."
Re: compiler errors: md needed for hardware raid?
Lars Oeschey <[EMAIL PROTECTED]> writes: > when trying to compile the 2.4.21 kernel I get compiler errors within > /drivers/md: > > In file included from xor.c:23: > /usr/src/kernel-source-2.4.21/include/asm/xor.h:35:5: missing > terminating " character Eek. That file uses multiline string literals, which is no longer accepted by gcc. You could just start each line within the asm argument with " and finish with \n\t". > I couldn't find anything on this error at google, so my question is: is > the md driver needed for hardware raids or is it just for software > raids? Software. -- Falk