All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Varoqui <christophe.varoqui@free.fr>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Re: [PATCH 2/4] multipath-tools: install libmultipath.so in $syslibdir
Date: Wed, 22 Apr 2009 22:44:28 +0200	[thread overview]
Message-ID: <1240433068.32381.3.camel@plop> (raw)
In-Reply-To: <20090419223620.GA9385@redhat.com>


> > 
> > Mike,
> > am I missing something ... I don't the lib/lib64 switching code.
> 
> The standard install would still just place libmultipath.so in /lib but
> this patch exposes the ability to override the default e.g.:
> make install syslibdir=/lib64 libdir=/lib64/multipath
> 
> The path checker and prioritizer modules would get installed in
> /lib64/multipath and libmultipath.so in /lib64
> 
Oh ok, I was expecting some kind of detection code to set /lib64.
I understand that this approach is sufficient for your packagers needs.

Thanks for explaining.

  reply	other threads:[~2009-04-22 20:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 22:07 [PATCH 0/4] Various small multipath-tools improvements Mike Snitzer
2009-04-17 22:07 ` [PATCH 1/4] multipath-tools: update scsi_id arguments Mike Snitzer
2009-04-17 22:07 ` [PATCH 2/4] multipath-tools: install libmultipath.so in $syslibdir Mike Snitzer
2009-04-19 22:10   ` Christophe Varoqui
2009-04-19 22:36     ` Mike Snitzer
2009-04-22 20:44       ` Christophe Varoqui [this message]
2009-04-17 22:07 ` [PATCH 3/4] multipath-tools: update multipathd.init.redhat Mike Snitzer
2009-04-17 22:08 ` [PATCH 4/4] multipath-tools: change default location for bindings file Mike Snitzer
2009-04-18 17:41 ` [PATCH 0/4] Various small multipath-tools improvements christophe.varoqui
2009-04-18 17:53   ` Mike Snitzer

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=1240433068.32381.3.camel@plop \
    --to=christophe.varoqui@free.fr \
    --cc=dm-devel@redhat.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.