From: "Josh Boyer" <jwboyer@gmail.com>
To: dbyron@hheld.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: autoconf for mtd-utils
Date: Sun, 30 Jul 2006 13:09:51 -0500 [thread overview]
Message-ID: <625fc13d0607301109k43537c7xfe045d288c018fe0@mail.gmail.com> (raw)
In-Reply-To: <000c01c6ab7b$9aa01f70$a134800a@RudiDell>
On 7/19/06, David Byron <dbyron@hheld.com> wrote:
> On Wed, 2006-07-19 at 12:25p, David Woodhouse wrote:
>
> > If you just send a proper Makefile patch which provides
> > separate source and build directories, that'd be useful
> > though.
>
> Like this?
Something like that. But leave the definition of CROSS alone. It's
better to leave the trailing '-' at the end so that if other cross
tools are needed, you just specify $(CROSS)ld, etc.
josh
next prev parent reply other threads:[~2006-07-30 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 21:37 autoconf for mtd-utils David Byron
2006-07-30 18:09 ` Josh Boyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-01 19:25 David Byron
2006-08-02 11:00 ` Josh Boyer
2006-08-03 12:22 ` Josh Boyer
2006-07-31 17:47 David Byron
2006-08-01 0:50 ` Josh Boyer
2006-07-19 18:52 David Byron
2006-07-19 19:24 ` David Woodhouse
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=625fc13d0607301109k43537c7xfe045d288c018fe0@mail.gmail.com \
--to=jwboyer@gmail.com \
--cc=dbyron@hheld.com \
--cc=linux-mtd@lists.infradead.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