Linux LVM users
 help / color / mirror / Atom feed
From: "bmoon" <bo@anthologysolutions.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Painless upgrade to lvm2?
Date: Tue Dec  3 13:46:01 2002	[thread overview]
Message-ID: <02bb01c29b04$31556650$6a01a8c0@bmoon> (raw)
In-Reply-To: 1038231397.21369.23.camel@defiant.sonsofthunder.yi.org

Hello,

I followed the instruction but I am facing the following cimpile error.
Would you provide me any help on this error?

---------------
make[1]: Entering directory `/usr/src/device-mapper.0.96.07/lib'
gcc -c -Iioctl -I. -I../include -I/usr/src/linux/include -Wall -fPIC -g -fno
-omit-frame-pointer ioctl/libdevmapper.c -o ioctl/libdevmapper.o
gcc -c -Iioctl -I. -I../include -I/usr/src/linux/include -Wall -fPIC -g -fno
-omit-frame-pointer libdm-common.c -o libdm-common.o
gcc -shared -Wl,-soname,libdevmapper.so.0.96 \
-Wl,--version-script,.export.sym ioctl/libdevmapper.o libdm-common.o -o
ioctl/libdevmapper.so
/usr/bin/ld:.export.sym:1: parse error in VERSION script
collect2: ld returned 1 exit status
make[1]: *** [ioctl/libdevmapper.so] Error 1
make[1]: Leaving directory `/usr/src/device-mapper.0.96.07/lib'
make: *** [lib] Error 2
--------------------------

Additional question, If I use linux2.4.20 then Are there any patches for it
or we do not need
any patch for LVM2 or device mapper?

Thanks in advance,

Bo

----- Original Message -----
From: "Bradley Alexander" <storm@tux.org>
To: <linux-lvm@sistina.com>
Sent: Monday, November 25, 2002 5:36 AM
Subject: [linux-lvm] Painless upgrade to lvm2?


> I'm running lvm-1.0.6 on a Debian/sid system, and was wondering what
> would be the best upgrade path? Install from debs? From source? Is there
> some kind of howto for making this transition?
>
> Thanks,
> --
> --Brad
>
============================================================================
> Bradley M. Alexander                |
> Debian Developer, Security Engineer |   storm [at] tux.org
> Debian/GNU Linux Developer          |   storm [at] debian.org
>
============================================================================
> Key fingerprints:
> DSA 0x54434E65: 37F6 BCA6 621D 920C E02E  E3C8 73B2 C019 5443 4E65
> RSA 0xC3BCBA91: 3F 0E 26 C1 90 14 AD 0A  C8 9C F0 93 75 A0 01 34
>
============================================================================
> Stay out of clouds. The silver lining everyone keeps talking
> about might be another airplane going in the opposite direction.
> Reliable sources also report that mountains have been known to hide
> out in clouds.
> --Rules of the Air, #13
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>

  parent reply	other threads:[~2002-12-03 13:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25  7:37 [linux-lvm] Painless upgrade to lvm2? Bradley Alexander
2002-11-25  8:23 ` Heinz J . Mauelshagen
2002-11-26  2:42   ` [linux-lvm] " Andres Salomon
2002-12-03 13:46 ` bmoon [this message]
2002-12-03 14:11   ` [linux-lvm] " Alasdair G Kergon
2002-12-04  6:10   ` Heinz J . Mauelshagen
2002-12-06 20:11     ` bmoon
2002-12-09  5:20       ` Heinz J . Mauelshagen

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='02bb01c29b04$31556650$6a01a8c0@bmoon' \
    --to=bo@anthologysolutions.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