From: Dan Nicholson <dbn.lists@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH 2/2] libvolume_id: Don't create /usr hierarchy when ${prefix}
Date: Fri, 26 Oct 2007 19:00:38 +0000 [thread overview]
Message-ID: <1193425238-4278-3-git-send-email-dbn.lists@gmail.com> (raw)
When libvolume_id is being installed to a non-/ location such as
/usr/local, we don't want to setup the /usr/{include,lib} hierarchy.
GNU make conditionals are used to separate the case where prefix is
unset or is / and retains the current udev behavior. When prefix is
something else, libvolume_id will be installed in a flat fashion.
Signed-off-by: Dan Nicholson <dbn.lists@gmail.com>
---
| 14 ++++++++++++--
1 files changed, 12 insertions(+), 2 deletions(-)
--git a/extras/volume_id/lib/Makefile b/extras/volume_id/lib/Makefile
index b553111..f0cfba4 100644
--- a/extras/volume_id/lib/Makefile
+++ b/extras/volume_id/lib/Makefile
@@ -4,9 +4,19 @@
#
# Released under the GNU General Public License, version 2.
#
-includedir = ${prefix}/usr/include
+ifndef prefix
+includedir = /usr/include
+libdir = /lib
+usrlibdir = /usr/lib
+else ifeq (${prefix},/)
+includedir = /usr/include
+libdir = /lib
+usrlibdir = /usr/lib
+else
+includedir = ${prefix}/include
libdir = ${prefix}/lib
-usrlibdir = ${prefix}/usr/lib
+usrlibdir = ${prefix}/lib
+endif
INSTALL = install -c
INSTALL_DATA = ${INSTALL} -m 644
--
1.5.3.2
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2007-10-26 19:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1193425238-4278-3-git-send-email-dbn.lists@gmail.com \
--to=dbn.lists@gmail.com \
--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).