From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] make env
Date: Thu, 20 Mar 2008 21:02:58 +0100 [thread overview]
Message-ID: <20080320200258.9DFE324A87@gemini.denx.de> (raw)
In-Reply-To: Your message of "Thu, 20 Mar 2008 18:56:06 +0100." <20080320175606.GA21970@michl.2n.cz>
In message <20080320175606.GA21970@michl.2n.cz> you wrote:
> On Thu, Mar 20, 2008 at 05:04:35PM +0100, Wolfgang Denk wrote:
> > I guess (you fail to mention such a basic fact as which version you
> > are using) that you are referring to old code. So I recommend to use
> > recent code (i. e. release 1.3.2).
>
> No matter how recent version is he going to use. Related Makefile
> fragment reads:
> env:
> $(MAKE) -C tools/env all MTD_VERSION=${MTD_VERSION} || exit 1
>
> which means CFLAGS etc. are not propagated to fw_setenv utility...
Yes, and actually I think this is correct. What we're building is a
target Linux application, so the U-Boto specific CFLAG settings have
no meaning for this (or rather would be just dangerous).
Example:
-> make env
make -C tools/env all MTD_VERSION= || exit 1
make[1]: Entering directory `/home/wd/git/u-boot/work/tools/env'
ln -s ../../lib_generic/crc32.c crc32.c
make[1]: Leaving directory `/home/wd/git/u-boot/work/tools/env'
make[1]: Entering directory `/home/wd/git/u-boot/work/tools/env'
arm-linux-gcc -Wall -DUSE_HOSTCC crc32.c fw_env.c fw_env_main.c -o
fw_printenv
make[1]: Leaving directory `/home/wd/git/u-boot/work/tools/env'
-> file tools/env/fw_printenv
tools/env/fw_printenv: ELF 32-bit LSB executable, ARM, version 1, dynamically linked (uses shared libs), for GNU/Linux 2.4.3, not stripped
I'm not sure what you wanted to express with your comment?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"I think trash is the most important manifestation of culture we have
in my lifetime." - Johnny Legend
next prev parent reply other threads:[~2008-03-20 20:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 15:57 [U-Boot-Users] make env Manuel Sahm
2008-03-20 16:04 ` Wolfgang Denk
2008-03-20 17:56 ` Ladislav Michl
2008-03-20 20:02 ` Wolfgang Denk [this message]
2008-03-20 20:11 ` Ladislav Michl
2008-03-20 21:27 ` Wolfgang Denk
2008-03-20 21:33 ` Ladislav Michl
2008-03-25 12:56 ` Manuel Sahm
2008-03-25 13:36 ` Markus Klotzbücher
2008-03-25 16:19 ` Manuel Sahm
2008-03-25 17:04 ` Markus Klotzbücher
2008-03-25 20:11 ` Wolfgang Denk
2008-04-02 9:31 ` Manuel Sahm
2008-04-02 10:39 ` Wolfgang Denk
2008-04-02 11:18 ` Manuel Sahm
2008-04-02 14:33 ` Wolfgang Denk
2008-04-06 17:37 ` Markus Klotzbücher
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=20080320200258.9DFE324A87@gemini.denx.de \
--to=wd@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