From: Jim Meyering <jim@meyering.net>
To: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
Cc: device-mapper development <dm-devel@redhat.com>,
LVM2 development <lvm-devel@redhat.com>
Subject: Re: [lvm-devel] new device-mapper required to build latest lvm from cvs
Date: Sat, 28 Jul 2007 15:06:46 +0200 [thread overview]
Message-ID: <87sl78wuc9.fsf@rho.meyering.net> (raw)
In-Reply-To: <46A7AB23.7050306@ce.jp.nec.com> (Jun'ichi Nomura's message of "Wed\, 25 Jul 2007 15\:57\:23 -0400")
"Jun'ichi Nomura" <j-nomura@ce.jp.nec.com> wrote:
> Jim Meyering wrote:
>> FYI, with the change I've just committed,
>>
>> http://sources.redhat.com/ml/lvm2-cvs/2007-07/msg00035.html
>>
>> you now need a device-mapper library and headers built from
>> today's cvs sources. Otherwise, you'll get compile warnings
>> and eventually a link error complaining about missing dm_fclose.
>
> This change introduces an error for static build.
Thank you for the report and the patches.
I've applied four of your patches, three for device-mapper
and one for lvm2:
dm
Export dm_create_dir (was create_dir) to help fix LVM2 link error
http://git.et.redhat.com/?p=device-mapper.git;a=commitdiff;h=8748390a79f
Don't log mkdir fail-with-EROFS, to make create_dir equiv to that in LVM2
http://git.et.redhat.com/?p=device-mapper.git;a=commitdiff;h=81d93dd4717
Introduce and use log_sys_* macros from LVM2
http://git.et.redhat.com/?p=device-mapper.git;a=commitdiff;h=5edca96def8
lvm2
Remove create_dir function; use now-equivalent dm_create_dir instead
http://git.et.redhat.com/?p=lvm2.git;a=commitdiff;h=7d85f48b35b7
WARNING: multiple messages have this Message-ID (diff)
From: Jim Meyering <jim@meyering.net>
To: lvm-devel@redhat.com
Subject: new device-mapper required to build latest lvm from cvs
Date: Sat, 28 Jul 2007 15:06:46 +0200 [thread overview]
Message-ID: <87sl78wuc9.fsf@rho.meyering.net> (raw)
In-Reply-To: <46A7AB23.7050306@ce.jp.nec.com> (Jun'ichi Nomura's message of "Wed\, 25 Jul 2007 15\:57\:23 -0400")
"Jun'ichi Nomura" <j-nomura@ce.jp.nec.com> wrote:
> Jim Meyering wrote:
>> FYI, with the change I've just committed,
>>
>> http://sources.redhat.com/ml/lvm2-cvs/2007-07/msg00035.html
>>
>> you now need a device-mapper library and headers built from
>> today's cvs sources. Otherwise, you'll get compile warnings
>> and eventually a link error complaining about missing dm_fclose.
>
> This change introduces an error for static build.
Thank you for the report and the patches.
I've applied four of your patches, three for device-mapper
and one for lvm2:
dm
Export dm_create_dir (was create_dir) to help fix LVM2 link error
http://git.et.redhat.com/?p=device-mapper.git;a=commitdiff;h=8748390a79f
Don't log mkdir fail-with-EROFS, to make create_dir equiv to that in LVM2
http://git.et.redhat.com/?p=device-mapper.git;a=commitdiff;h=81d93dd4717
Introduce and use log_sys_* macros from LVM2
http://git.et.redhat.com/?p=device-mapper.git;a=commitdiff;h=5edca96def8
lvm2
Remove create_dir function; use now-equivalent dm_create_dir instead
http://git.et.redhat.com/?p=lvm2.git;a=commitdiff;h=7d85f48b35b7
next prev parent reply other threads:[~2007-07-28 13:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 17:51 new device-mapper required to build latest lvm from cvs Jim Meyering
2007-07-25 19:57 ` [lvm-devel] " Jun'ichi Nomura
2007-07-25 19:57 ` Jun'ichi Nomura
2007-07-25 20:01 ` [lvm-devel] " Jun'ichi Nomura
2007-07-25 20:01 ` Jun'ichi Nomura
2007-07-25 20:10 ` Alasdair G Kergon
2007-07-25 20:32 ` Alasdair G Kergon
2007-07-25 21:04 ` Jun'ichi Nomura
2007-07-26 18:38 ` Jun'ichi Nomura
2007-07-26 20:34 ` Jun'ichi Nomura
2007-07-26 18:39 ` Jun'ichi Nomura
2007-07-25 20:43 ` Jun'ichi Nomura
2007-07-28 13:06 ` Jim Meyering [this message]
2007-07-28 13:06 ` 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=87sl78wuc9.fsf@rho.meyering.net \
--to=jim@meyering.net \
--cc=dm-devel@redhat.com \
--cc=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.