From: Artem Bityutskiy <dedekind@infradead.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] unify all common build system parts
Date: Fri, 12 Dec 2008 09:19:05 +0200 [thread overview]
Message-ID: <1229066345.13686.413.camel@sauron> (raw)
In-Reply-To: <1228944506-5792-1-git-send-email-vapier@gentoo.org>
On Wed, 2008-12-10 at 16:28 -0500, Mike Frysinger wrote:
> Rather than duplicating the same thing over and over in every Makefile, move
> it all to common.mk.
>
> Other things fixed here:
> - doing subdirs in parallel
> - fix src!=build compiling in subdirs
>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
I've tried do test your patch and found an issue.
$ make
... build is ok ...
$ make install DESTDIR=/home/dedekind/tmp/
... error ...
Could you please take a look at this?
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-12-12 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 21:28 [PATCH] unify all common build system parts Mike Frysinger
2008-12-11 6:14 ` Artem Bityutskiy
2008-12-11 9:12 ` Mike Frysinger
2008-12-12 7:19 ` Artem Bityutskiy [this message]
2008-12-16 9:07 ` Mike Frysinger
2008-12-18 20:21 ` Mike Frysinger
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=1229066345.13686.413.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier@gentoo.org \
/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