From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tools/env: fix cross-compilation
Date: Sun, 8 Jan 2012 01:54:53 -0500 [thread overview]
Message-ID: <201201080154.53648.vapier@gentoo.org> (raw)
In-Reply-To: <37B23A30-672C-4717-9AE4-27D512462849@gmail.com>
On Thursday 05 January 2012 18:25:52 Grant Erickson wrote:
> On Jan 5, 2012, at 3:18 PM, Mike Frysinger wrote:
> > On Thursday 22 December 2011 13:39:35 Grant Erickson wrote:
> >> This patch fixes the make infrastructure for the fw_printenv tool such
> >> that it is built, by default, as a cross-compilation for the target
> >> board when so requested with TOOLSUBDIRS on the U-Boot make command
> >> line.
> >
> > how is this any simpler than the existing method ?
> >
> > make tools HOSTCC=some-random-target-gcc
> >
> > the current tools/ subdir is consistent in its handling. this patch
> > would break that.
>
> Because it's broken with respect to how the rest of U-Boot is built. I
> already specify the cross-compiler via CROSS_COMPILE when I build
> u-boot.bin and u-boot.img, that I need to specify the same compiler in two
> different ways to build executables for the same target platform is broken
> and, it sounds like, as are the rest of the tools subdirectories.
no, you specified the toolchain that is appropriate for building bare metal
code. it is often times not the same as the toolchain used to build userspace
applications for running under Linux. this is not broken behavior.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120108/ac613bb7/attachment.pgp>
prev parent reply other threads:[~2012-01-08 6:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 18:39 [U-Boot] [PATCH] tools/env: fix cross-compilation Grant Erickson
2012-01-05 23:18 ` Mike Frysinger
2012-01-05 23:25 ` Grant Erickson
2012-01-08 6:54 ` Mike Frysinger [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=201201080154.53648.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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