From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] makefiles: fixes for building build tools
Date: Fri, 4 Dec 2009 04:45:07 +0100 [thread overview]
Message-ID: <200912040445.07422.sr@denx.de> (raw)
In-Reply-To: <4B180CF9.4030401@freescale.com>
On Thursday 03 December 2009 20:09:45 Scott Wood wrote:
> > Hmmm. I don't see this here. Do you only see this for katmai, or for
> > other 4xx targets as well? kilauea, sequoia?
>
> Looks like all of them.
Thanks. I'll try to investigate here further soon.
<snip>
> > So the complete tools directory is compiled for powerpc!
>
> Actually, it looks like it's just the files whose sources live somewhere
> else (look at envcrc.c, for example). Those files should be hitting these
> rules inside tools/Makefile:
>
> # Some of the tool objects need to be accessed from outside the tools
> directory $(obj)%.o: $(SRCTREE)/common/%.c
> $(HOSTCC) -g $(HOSTCFLAGS_NOPED) -c -o $@ $<
>
> $(obj)%.o: $(SRCTREE)/lib_generic/%.c
> $(HOSTCC) -g $(HOSTCFLAGS) -c -o $@ $<
>
> Do you by any chance have a copy of/link to crc32.c, env_embedded.c, etc.
> sitting in your tools directory, allowing it to match the normal pattern
> rule?
Yes. I had links of those files there. After removing those it works fine.
Thanks.
Cheers,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
prev parent reply other threads:[~2009-12-04 3:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 0:41 [U-Boot] [PATCH v2] makefiles: fixes for building build tools Scott Wood
2009-11-13 18:51 ` Mike Frysinger
2009-11-13 18:53 ` Scott Wood
2009-11-13 23:07 ` Mike Frysinger
2009-12-02 21:59 ` Wolfgang Denk
2009-12-03 7:26 ` Stefan Roese
2009-12-03 17:49 ` Scott Wood
2009-12-03 18:17 ` Stefan Roese
2009-12-03 19:09 ` Scott Wood
2009-12-04 3:45 ` Stefan Roese [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=200912040445.07422.sr@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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