From: Thomas Koeller <thomas@koeller.dyndns.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 21:35:14 +0000 [thread overview]
Message-ID: <200807092335.15214.thomas@koeller.dyndns.org> (raw)
In-Reply-To: <1215468723-18298-2-git-send-email-thomas@koeller.dyndns.org>
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.
Thomas
On Mittwoch, 9. Juli 2008, Kay Sievers wrote:
> On Tue, Jul 8, 2008 at 08:53, Harald Hoyer <harald@redhat.com> wrote:
> > Thomas Koeller wrote:
> >> Installing 64-bit libraries in /lib and /usr/lib
> >> is wrong.
> >
> > Fedora has the attached patch and builds on 64bit systems with:
> > $ make libdir="/lib64" usrlibdir="/usr/lib64" ...
>
> This is not needed, it works fine without the patch. We all do it that
> way for long.
>
> > diff -up udev-120/extras/volume_id/lib/Makefile.lib64
> > udev-120/extras/volume_id/lib/Makefile
> > + $(INSTALL_LIB) -D libvolume_id.a
>
> What would be the point to package an intermediate internal udev build
> file?. This is not a library, and nothing that should be distributed
> with a package.
>
> Thanks,
> Kay
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Thomas Koeller
thomas@koeller.dyndns.org
next prev parent reply other threads:[~2008-07-09 21:35 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 [this message]
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
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=200807092335.15214.thomas@koeller.dyndns.org \
--to=thomas@koeller.dyndns.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).