From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Compiling fw_printenv tool
Date: Fri, 17 Jan 2014 17:02:54 +0100 [thread overview]
Message-ID: <m24n52egup.fsf@lamuella.denx.de> (raw)
In-Reply-To: <52D94113.9030300@xtech2.lv> (Alexey Smishlayev's message of "Fri, 17 Jan 2014 16:41:23 +0200")
Hi Alexey,
[...]
> In case someone needs that (before the Makefile changes are accepted),
> I used the
>
> make HOSTCC='arm-none-linuex-gnueabi-gcc -static' env
> command to get it working.
We usually do put options into the HOSTCC variable. Of course one can
argue about that, but the make documentation says about CC:
`CC'
Program for compiling C programs; default `cc'.
and about
`CFLAGS'
Extra flags to give to the C compiler.
So maybe you can do the same in a cleaner way like
make HOSTCC='arm-none-linux-gnueabi-gcc' HOSTCFLAGS='-static' env
Don't get me wrong, I don't want to win a beauty contest, but my
experience tells me that such "oh this works for me" quick and dirty
solutions tend to build up "debt" that can be hard to pay later on ;)
Cheers
Detlev
--
The best way to predict the future is to invent it.
-- Alan Kay
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2014-01-17 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 10:53 [U-Boot] Compiling fw_printenv tool Alexey Smishlayev
2013-11-29 11:17 ` Detlev Zundel
2013-11-29 12:50 ` Alexey Smishlayev
2014-01-14 10:54 ` Detlev Zundel
2014-01-14 11:25 ` Alexey Smishlayev
2014-01-17 14:30 ` Detlev Zundel
2014-01-17 14:41 ` Alexey Smishlayev
2014-01-17 16:02 ` Detlev Zundel [this message]
2014-01-14 11:47 ` Masahiro Yamada
2014-01-15 14:50 ` Gerhard Sittig
2014-01-17 14:38 ` Detlev Zundel
2014-01-17 14:28 ` Detlev Zundel
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=m24n52egup.fsf@lamuella.denx.de \
--to=dzu@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