From: Alasdair G Kergon <agk@redhat.com>
To: John Taylor <pi00100100@gmail.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Problems at cross-compiling LVM2-2.02.52
Date: Tue, 22 Sep 2009 13:47:14 +0100 [thread overview]
Message-ID: <20090922124714.GM1210@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <c9048c0a0909220516o23075a6h88111b4f42df3039@mail.gmail.com>
On Tue, Sep 22, 2009 at 02:16:16PM +0200, John Taylor wrote:
> I have some problems at cross-compiling LVM2-2.02.52 (latest release).
> The configure argument list is: --prefix=/usr
> --build=i486-unknown-linux-gnu --host=x86_64-unknown-linux-gnu
> --target=x86_64-unknown-linux-gnu --disable-nls. First of all, I
> noticed I can't build LVM2 from a directory different than that where
> I extracted the source tarball, because I get the following error when
> running make:
> make -C doc device-mapper
> make[1]: Entering directory `/mnt/clfs/sources/lvm2-build/doc'
> Makefile:21: ../../LVM2-2.02.52/make.tmpl: No such file or directory
> make[1]: *** No rule to make target `../../LVM2-2.02.52/make.tmpl'. Stop.
> make[1]: Leaving directory `/mnt/clfs/sources/lvm2-build/doc'
> make: *** [doc.device-mapper] Error 2
Paths are stored by 'configure' - that could be where the problem is, if
the code is moved after running configure, or a path with symlinks is
supplied (so .. goes to the wrong place).
The top of my Makefile is:
srcdir = .
top_srcdir = .
'make' is designed only to be run from the top directory of the tree,
not subdirectories.
But your example makes no sense: there is nothing to do for
'device-mapper' in 'doc', and it works for me anyway, both with -C and
using the alternative internal 'dot' target directly.
$ make -C doc device-mapper
make: Entering directory `/d/LVM2/doc'
make: Nothing to be done for `device-mapper'.
make: Leaving directory `/d/LVM2/doc'
$ make doc.device-mapper
make -C doc device-mapper
make[1]: Entering directory `/d/LVM2/doc'
make[1]: Nothing to be done for `device-mapper'.
make[1]: Leaving directory `/d/LVM2/doc'
Alasdair
next prev parent reply other threads:[~2009-09-22 12:47 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 [this message]
2009-09-22 13:04 ` John Taylor
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=20090922124714.GM1210@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=pi00100100@gmail.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).