From: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
To: lvm-devel@redhat.com
Subject: RFC: testing framework
Date: Fri, 14 Sep 2007 19:14:36 -0400 [thread overview]
Message-ID: <46EB15DC.4060901@ce.jp.nec.com> (raw)
In-Reply-To: <46EB151D.2080305@ce.jp.nec.com>
Jun'ichi Nomura wrote:
> Jim Meyering wrote:
>> There are kludges in t/Makefile.in (symlink creation and LD_LIBRARY_PATH
>> setting), that are required to run the dynamically-linked lvm against the
>> libraries in a just-compiled sibling device-mapper directory. Thanks to
>> Dave Wysochanski for that tip. IMHO this is a very strong argument
>> for pulling device-mapper into lvm. Alasdair, can we do that soon?
>> I'll be happy to submit a patch.
>
> It didn't work for me because I have device-mapper source directory
> named '../device-mapper.work', instead of '../device-mapper' that
> Makefile assumes.
> There is '--with-dmdir=DIR' option for configure.
> Can the Makefile use it?
> (A patch is attached.)
Also, this patch to allow relative path for '--with-dmdir' might
be helpful.
Thanks,
--
Jun'ichi Nomura, NEC Corporation of America
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lvm2-configure-allow-relative-path.patch
Type: text/x-patch
Size: 447 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/lvm-devel/attachments/20070914/7833087c/attachment.bin>
next prev parent reply other threads:[~2007-09-14 23:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 18:55 RFC: testing framework Jim Meyering
2007-09-14 23:11 ` Jun'ichi Nomura
2007-09-14 23:14 ` Jun'ichi Nomura [this message]
2007-09-17 10:35 ` Jim Meyering
2007-09-17 11:56 ` Jim Meyering
2007-09-17 18:15 ` Alasdair G Kergon
2007-09-17 19:04 ` Alasdair G Kergon
2007-09-17 20:55 ` Jim Meyering
2007-09-17 21:45 ` Alasdair G Kergon
2007-09-18 13:03 ` Jim Meyering
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=46EB15DC.4060901@ce.jp.nec.com \
--to=j-nomura@ce.jp.nec.com \
--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.