From: David Gibson <david@gibson.dropbear.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Jon Loeliger <jdl@jdl.com>,
stuarth@freescale.com
Subject: Re: [DTC][PATCH] Fix cross-compile building
Date: Mon, 17 Dec 2007 16:39:20 +1100 [thread overview]
Message-ID: <20071217053920.GD3477@localhost.localdomain> (raw)
In-Reply-To: <A388C2C2-2452-4E70-A5DA-F61B0E3A2B22@kernel.crashing.org>
On Thu, Dec 13, 2007 at 11:57:48PM -0600, Kumar Gala wrote:
>
> On Dec 7, 2007, at 6:36 PM, David Gibson wrote:
>
> > On Fri, Dec 07, 2007 at 12:28:20PM -0600, Kumar Gala wrote:
> >> From: Stuart Hughes <stuarth@freescale.com>
> >>
> >> This patch allows you to build the DTC source without making the
> >> tests directory. This is necessary when cross compiling as the
> >> dumptest (and other) files cannot be run/used on the host system.
> >> To use this use: 'make TESTS='
> >
> > I think this is a silly way of doing this. Instead create a new
> > target which builds everything but the tests.
> >
> > Say,
> >
> > all: cross tests
> >
> > cross: dtc ftdump libfdt
>
> shouldn't we do this the other way around, it seems odd to build the
> tests always or at least as part of the all target.
Hrm. Yeah, I guess so.
The idea was to encourage the tests to be used as much as possible,
but I guess there's not all that much value to building them without
running them.
Patch forthcoming.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
prev parent reply other threads:[~2007-12-17 5:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 18:28 [DTC][PATCH] Fix cross-compile building Kumar Gala
2007-12-08 0:36 ` David Gibson
2007-12-08 12:53 ` Stuart Hughes
2007-12-14 5:57 ` Kumar Gala
2007-12-17 5:39 ` David Gibson [this message]
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=20071217053920.GD3477@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=galak@kernel.crashing.org \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=stuarth@freescale.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.