From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problems compiling 2.4.4
Date: Fri, 4 May 2001 09:38:09 +0000 [thread overview]
Message-ID: <20010504093809.F4700@sistina.com> (raw)
In-Reply-To: <3AF092F1.4196DB9B@gecpalau.com>; from glenn@gecpalau.com on Thu, May 03, 2001 at 08:06:25AM +0900
Glenn is right.
I've already applied support for the changed symbol (get_hardsect_size rather
than get_hardblocksize) in recent LVM CVS.
Regards,
Heinz -- The LVM Guy --
On Thu, May 03, 2001 at 08:06:25AM +0900, Glenn Shannon wrote:
> Emanuel Quass wrote:
>
> > Hi,
> >
> > I compiled a kernel(2.4.4) with your lvm patch (0.9.1_beta7).
> > At the end of make bzImage an error occours:
> >
> > ld -m elf_i386 -T /mnt/kernel/linux/arch/i386/vmlinux.lds -e \
> > stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o \
> > init/main.o init/version.o \
> > --start-group \
> > arch/i386/kernel/kernel.o arch/i386/mm/mm.o \
> > kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \
> > drivers/block/block.o drivers/char/char.o \
> > drivers/misc/misc.o drivers/net/net.o drivers/media/media.o \
> > drivers/ide/idedriver.o drivers/scsi/scsidrv.o \
> > drivers/cdrom/driver.o drivers/pci/driver.o drivers/video/video.o \
> > drivers/md/mddev.o \
> > net/network.o \
> > /mnt/kernel/linux/arch/i386/lib/lib.a \
> > /mnt/kernel/linux/lib/lib.a /mnt/kernel/linux/arch/i386/lib/lib.a \
> > --end-group \
> > -o vmlinux \
> > drivers/md/mddev.o: In function `__update_hardblocksize':
> > drivers/md/mddev.o(.text+0x2316): undefined reference to `get_hardblocksize'
> > drivers/md/mddev.o(.text+0x2352): undefined reference to `get_hardblocksize'
> > make: *** [vmlinux] Error 1
> > Does anybody knwo where this comes from!
> >
> > Thanks in advance
> >
> > Emanuel
> >
> > P.S. Please CC me because I am not in the list.
> >
> > --
> >
> > ++++++++++++++++++++++++++++++++
> > Emanuel Quass
> > email : emanuel.quass@temic.com
> >
> > In a world without fences and walls,
> > who needs Windows and Gates?
> > ++++++++++++++++++++++++++++++++
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
>
> go to your /usr/src/linux directory.....go to drivers/md and edit lvm.c and
> change the two entries of get_hardblocksize with get_hardsect_size
>
> That should do the trick.
>
> Glenn
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
*** 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:[~2001-05-04 9:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-02 16:28 [linux-lvm] Problems compiling 2.4.4 Emanuel Quass
2001-05-02 23:06 ` Glenn Shannon
2001-05-04 9:38 ` Heinz J. Mauelshagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-02 23:19 Lionel COTTIN
2001-05-02 23:29 ` Glenn Shannon
2001-05-02 23:20 Day, Evan
2001-05-02 23:54 Day, Evan
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=20010504093809.F4700@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.