From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH 2/2] Fixed installation path for 64-bit libvolume_id.so
Date: Wed, 09 Jul 2008 22:45:58 +0000 [thread overview]
Message-ID: <1215643558.347.21.camel@linux.site> (raw)
In-Reply-To: <1215468723-18298-2-git-send-email-thomas@koeller.dyndns.org>
On Thu, 2008-07-10 at 00:41 +0200, Thomas Koeller wrote:
> On Mittwoch, 9. Juli 2008, Kay Sievers wrote:
> > On Wed, Jul 9, 2008 at 23:35, Thomas Koeller <thomas@koeller.dyndns.org>
> wrote:
> > > When building with 'USE_STATIC = false' in the top level Makefile, which
> > > is the default, a shared library is generated which of course needs to be
> > > installed.
> >
> > It's a .a, which is a static lib, not a shared one which is obviously
> > installed by default. But still, why would someone need that "lib",
> > which is usually only build to create a static vol_id?
>
> This is from extras/volume_id/lib/Makefile:
>
> SHLIB = libvolume_id.so.$(SHLIB_CUR).$(SHLIB_REV).$(SHLIB_AGE)
> ...
> all: libvolume_id.a $(SHLIB) libvolume_id.pc
>
>
> As you can see, a shared libvolume_id.so is built, and this is what
> actually happens when invoking make with the Makefile unmodified. Try
> it if you don't believe me.
Sure, I obviously know what that Makefile does. :)
But in the patch, it's about the .a file, not the .so:
> udev-120/extras/volume_id/lib/Makefile
> + $(INSTALL_LIB) -D libvolume_id.a
Kay
next prev parent reply other threads:[~2008-07-09 22:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 22:12 [PATCH 2/2] Fixed installation path for 64-bit libvolume_id.so Thomas Koeller
2008-07-08 6:53 ` Harald Hoyer
2008-07-09 19:51 ` Thomas Koeller
2008-07-09 21:26 ` Kay Sievers
2008-07-09 21:35 ` Thomas Koeller
2008-07-09 21:44 ` Kay Sievers
2008-07-09 22:03 ` Dan Nicholson
2008-07-09 22:41 ` Thomas Koeller
2008-07-09 22:45 ` Kay Sievers [this message]
2008-07-09 23:04 ` Thomas Koeller
2008-07-22 13:59 ` Kay Sievers
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=1215643558.347.21.camel@linux.site \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).