public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [WIP] tools/env: cleanup host build flags
Date: Wed, 10 Nov 2010 17:06:16 -0500	[thread overview]
Message-ID: <201011101706.17988.vapier@gentoo.org> (raw)
In-Reply-To: <20101110200048.9D3151522C0@gemini.denx.de>

On Wednesday, November 10, 2010 15:00:48 Wolfgang Denk wrote:
> Mike Frysinger wrote:
> > > - use the cross compiler again (fw_printenv is intended for a
> > > 
> > >   hosted environment on the target).
> > 
> > the cross-compiler used to create u-boot has no guarantee that it'll
> > produce executables useful for the target OS.  often this isnt the case.
> >  HOSTCC
> 
> Really? You mean, you need different tool chains to build U-Boot, the
> Linux kernel or user space applications?  Frankly, I consider those
> tool chains broken.

based on your based comments, i'm really not surprised.  you constantly prefer 
to ignore reality and the state of GNU toolchains.  plus, you ignore other 
obvious setups.  just because the toolchain in question may produce binaries 
doesnt mean the binaries are in the ABI format desired for linux userspace.

blindly assuming the toolchain that is being used to create u-boot will also 
be used for creating userspace apps is fundamentally wrong.

> > however will produce useful userspace applications for whatever host the
> > user has selection.
> 
> This makes no sense to me.  We have CROSS_COMPILE set, and that is
> supposed to be used for cross compilation.
> 
> IIRC, HOSTCC refers to the C compiler on the and for the build host,
> i. e. when running on a x86 system it will create x86 code.  This is
> obviously wrong when we try to build fw_printenv for, say, a PPC4xx
> system.

and it is trivial for the user to say "i wish to build tools for PPC4xx 
userland"
-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/20101110/1714b822/attachment.pgp 

  reply	other threads:[~2010-11-10 22:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11 16:06 [U-Boot] [WIP] tools/env: cleanup host build flags Daniel Hobi
2010-10-11 19:16 ` Scott Wood
2010-11-09 15:03 ` Detlev Zundel
2010-11-09 15:58   ` Steve Sakoman
2010-11-10  9:23 ` Mike Frysinger
2010-11-10 11:58   ` Daniel Hobi
2010-11-10 22:09     ` Mike Frysinger
2010-11-10 13:11   ` [U-Boot] [PATCH] " Daniel Hobi
2010-11-10 20:00   ` [U-Boot] [WIP] " Wolfgang Denk
2010-11-10 22:06     ` Mike Frysinger [this message]
2010-11-10 22:25       ` Wolfgang Denk
2010-11-10 22:51         ` Mike Frysinger
2010-11-10 22:12     ` Grant Edwards

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=201011101706.17988.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