From: John Taylor <pi00100100@gmail.com>
To: Alasdair G Kergon <agk@redhat.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Problems at cross-compiling LVM2-2.02.52
Date: Tue, 22 Sep 2009 15:04:09 +0200 [thread overview]
Message-ID: <4AB8CB49.2050409@gmail.com> (raw)
In-Reply-To: <20090922124714.GM1210@agk-dp.fab.redhat.com>
Alasdair G Kergon wrote:
> 'make' is designed only to be run from the top directory of the tree,
> not subdirectories.
I'm not running 'make' from a subdirectory of the sources directory, but
from a directory at its same level. That is, the sources directory is
/mnt/clfs/sources/LVM2-2.02.52, while the desired build directory is
/mnt/clfs/sources/lvm2-build. That's the way I usually build packages.
next prev parent reply other threads:[~2009-09-22 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 12:16 [linux-lvm] Problems at cross-compiling LVM2-2.02.52 John Taylor
2009-09-22 12:33 ` Alasdair G Kergon
2009-09-22 12:40 ` John Taylor
2009-09-22 12:47 ` Alasdair G Kergon
2009-09-22 13:04 ` John Taylor [this message]
2009-09-22 13:11 ` Alasdair G Kergon
2009-09-22 13:23 ` John Taylor
2009-09-22 13:40 ` Alasdair G Kergon
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=4AB8CB49.2050409@gmail.com \
--to=pi00100100@gmail.com \
--cc=agk@redhat.com \
--cc=linux-lvm@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 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).