From: David Gibson <david@gibson.dropbear.id.au>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org, scott.wood@freescale.com
Subject: Re: ep88xc_defconfig doesn't build
Date: Mon, 22 Oct 2007 11:17:12 +1000 [thread overview]
Message-ID: <20071022011712.GA18031@localhost.localdomain> (raw)
In-Reply-To: <20071022011740.GA25222@lixom.net>
On Sun, Oct 21, 2007 at 08:17:40PM -0500, Olof Johansson wrote:
> On Mon, Oct 22, 2007 at 10:36:25AM +1000, David Gibson wrote:
> > On Fri, Oct 19, 2007 at 09:43:55PM -0500, Olof Johansson wrote:
> > > Hi,
> > >
> > > Did it ever?! I get this with current mainline when building default target:
> >
> > I think you must have an old dtc; I'm pretty sure I removed the check
> > for /chosen some time ago. But then I also thought we added a force
> > to the dtc commant line in wrapper ages ago, so now I'm a bit confused.
>
> Hrm, seems like I had an old version. It's a little annoying that it's a
> moving target and it's impossible to find out form a built binary which
> version it is, besides trying to guess based on file time stamps.
>
> A nice enhancement could be to have a "dtc -v" and have the makefile
> verify it before using it.
Current dtc has a -v option. Trying to verify it in Makefile (or more
to the point in the wrapper script) would be a bit.. messy (since the
necessary version kind of depends on the dts file anyway).
Avoiding this sort of hassle is why I'd like to put a copy of dtc in
the kernel tree.
--
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
next prev parent reply other threads:[~2007-10-22 1:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-20 2:43 ep88xc_defconfig doesn't build Olof Johansson
2007-10-22 0:36 ` David Gibson
2007-10-22 1:17 ` Olof Johansson
2007-10-22 1:17 ` David Gibson [this message]
2007-10-22 1:23 ` Olof Johansson
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=20071022011712.GA18031@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=scott.wood@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 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).