From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problems with 1.0
Date: Fri, 17 Aug 2001 10:58:36 +0100 [thread overview]
Message-ID: <20010817105835.C709@tykepenguin.com> (raw)
In-Reply-To: <20010817110043.A10370@sistina.com>; from mauelshagen@sistina.com on Fri, Aug 17, 2001 at 11:00:43AM +0200
On Thu, Aug 16, 2001 at 10:55:35PM -0600, Tren Blackburn wrote:
> Hi List;
>
> 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.
libgcc_s.so.1 is new for GCC 3.0. gcc 2 statically linked libgcc. So it looks
like maybe you built beta8 with gcc 2 and 1.0 with gcc 3.
In any event, as Heinz says, libgcc.so.1 should be in /lib if gcc was correctly
installed - though if you are booting from an initrd it may not have found its
way onto that.
patrick
next prev parent reply other threads:[~2001-08-17 9:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 4:55 [linux-lvm] Problems with 1.0 Tren Blackburn
2001-08-17 9:00 ` Heinz J . Mauelshagen
2001-08-17 9:58 ` Patrick Caulfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-17 14:28 Tren Blackburn
2001-08-21 8:24 ` Jan Schreckenbach
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=20010817105835.C709@tykepenguin.com \
--to=caulfield@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox