From: agk@sourceware.org <agk@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW liblvm/Makefile.in
Date: 22 Jul 2009 20:12:15 -0000 [thread overview]
Message-ID: <20090722201215.23145.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk at sourceware.org 2009-07-22 20:12:14
Modified files:
. : WHATS_NEW
liblvm : Makefile.in
Log message:
Use newly-independent LVM_LIBAPI in liblvm soname. E.g. liblvm2app.so.2.1.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1196&r2=1.1197
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/liblvm/Makefile.in.diff?cvsroot=lvm2&r1=1.7&r2=1.8
--- LVM2/WHATS_NEW 2009/07/22 20:01:28 1.1196
+++ LVM2/WHATS_NEW 2009/07/22 20:12:14 1.1197
@@ -1,5 +1,6 @@
Version 2.02.50 -
================================
+ Use newly-independent LVM_LIBAPI in liblvm soname. E.g. liblvm2app.so.2.1.
Add an API version number, LVM_LIBAPI, to the VERSION string for liblvm.
Pass a pointer to struct cmd_context to init_multiple_segtypes
Return EINVALID_CMD_LINE not success when invalid VG name format is used.
--- LVM2/liblvm/Makefile.in 2009/07/14 03:02:14 1.7
+++ LVM2/liblvm/Makefile.in 2009/07/22 20:12:14 1.8
@@ -21,8 +21,8 @@
lvm_vg.c
LIB_NAME = liblvm2app
-LIB_VERSION = $(LIB_VERSION_LVM)
-VERSIONED_SHLIB = $(LIB_NAME).$(LIB_SUFFIX).$(LIB_VERSION_LVM)
+LIB_VERSION = $(LIB_VERSION_APP)
+VERSIONED_SHLIB = $(LIB_NAME).$(LIB_SUFFIX).$(LIB_VERSION_APP)
ifeq ("@STATIC_LINK@", "yes")
LIB_STATIC = $(LIB_NAME).a
next reply other threads:[~2009-07-22 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 20:12 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-29 19:24 LVM2 ./WHATS_NEW liblvm/Makefile.in agk
2012-02-08 10:52 zkabelac
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=20090722201215.23145.qmail@sourceware.org \
--to=agk@sourceware.org \
--cc=lvm-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.