All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Schreckenbach <Jan.Schreckenbach@sap.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problems with 1.0
Date: Tue, 21 Aug 2001 10:24:24 +0200	[thread overview]
Message-ID: <3B821AB8.1A324381@sap.com> (raw)
In-Reply-To: BJEHIDHMNHMANMFJEKAPGEAGCAAA.tren@eotnetworks.com

Tren Blackburn wrote:
[snipp]
> >> I had installed the 1.0 driver into my 2.4.8 kernel, and rebooted.
> >> Everything came up fine, so I installed the user tools and forgot about
> >> them...until I had to reboot this evening...Now the LVM tools are
> >> dynamically linked (Looking for libgcc_s.so.1)?  Or so it seems.  I am
> no
> >> a C programmer and don't fully understand how linking works, but it
> seems
> >> to me that the beta 8 tools were statically linked as they didn't need
> any
> >> external libraries, but the 1.0 user tools are dynamically linked.
> >>
> >> Now this probably doesn't seem like a problem, but when your libraries
> are
> >> mounted on a LVM volume and you have no tools to activate your volume
> >> with...well...you can probably guess  =)  Luckilly I had an identically
> >> configured machine that I hadn't upgraded to 1.0 yet (same gcc 3.0
> >> compiler, etc) so I just copied the tools across to the other machine
> >> (beta 8 tools) and all is fine again.
> >>
> >> If I am completely off base as to what is happening here, please
> correct
> >> me, and please also let me know how to solve this problem.>
> >
> >Tren,
> >that shouldn't be a problem because the default installation directory
> for
> >shared libraries is /lib which belongs to the root directory. LVM tools
> just
> >access any shread libraries from there unless you use the --libdir
> configure
> >option to chosse a different one.
> >
[snipp]
> Also, to answer another persons question, no, I did *not* build the beta 8
> tools with 2.9x.  Both beta8 and 1.0 were built with 3.0.  3.0 was built
> with 2.9x and then 2.9x was uninstalled.  The libraries for 3.0 sit in
> /usr/local/lib, not /lib.
> 
> So, the problem is with 1.0 tools, it needs access to a filesystem that is
> *not* mounted to load in the library.
> 

Hi,

you must not have a part of your base system on a partion
other than /. If you compile programms that are part of your
base system with gcc-3 you need to have the libraries in your
root-partition. 
The time you installed gcc-3 ist was a kind of add-on, because
you did not need it for any part of your base system. Therefore
it was OK to have it on /usr/local.
Reinstall gcc-3 on / or compile LVM with gcc-2.9x. You may
also do a ldd on every binary you need from LVM and copy
the libraries over to /lib.

cu,
Jan

--
_______________________________________________________________________

THE BEST RUN E-BUSINESSES RUN SAP
_______________________________________________________________________

Jan Schreckenbach                      email: Jan.Schreckenbach@sap.com
SAP AG Walldorf/Baden, Germany         Phone: +49 6227  7-47474
LinuxLab                               Fax  : +49 6227 78-31414

SAP LinuxLab support address: linux@sap.com

  reply	other threads:[~2001-08-21  8:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17 14:28 [linux-lvm] Problems with 1.0 Tren Blackburn
2001-08-21  8:24 ` Jan Schreckenbach [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-17  4:55 Tren Blackburn
2001-08-17  9:00 ` Heinz J . Mauelshagen
2001-08-17  9:58   ` Patrick Caulfield

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=3B821AB8.1A324381@sap.com \
    --to=jan.schreckenbach@sap.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.