From: Ben Warren <bwarren@qstreams.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH]: tools: fix fw_printenv tool to compile again
Date: Tue, 27 Nov 2007 17:30:03 -0500 [thread overview]
Message-ID: <474C9A6B.7000607@qstreams.com> (raw)
In-Reply-To: <20071127220619.9990124075@gemini.denx.de>
Wolfgang Denk wrote:
> In message <474C390C.8060007@qstreams.com> you wrote:
>
>> Sounds good to me. It'd be cooler if make could detect the
>> presence/absence of <linux/mtd-user.h>, but I'm not enough of a build
>> system whiz to know how to do that.
>>
>
> Where should he detect this? On the build host? Who says the target
> uses the same kernel / MTD version? Who says you always want to build
> for the same kernel / MTD version?
>
> I think auto-detection is basicly impossible (at least without making
> the build depending on the knowledge of a "corresponding" Linux
> kernel tree, and I think Markus' new approach is more
> straightforward.
>
>
Right. I said it would be cool, not necessarily possible. This brings
up a problem with this utility - the version of headers that it's built
against is at the mercy of however the cross compiler's set up, not
necessarily against the one the user really wants. Maybe we should
force the user to define a path, and #error if it isn't defined. This
path could be added to C_INCLUDE_PATH and then we could do all sorts of
Makefile trickery. Just a thought...
>> 1. Can you also please add the other part of my patch that
>> creates/destroys the 'fw_setenv' symbolic link? It's a bit annoying
>> that the documentation mentions the 'fw_setenv' utility, but it doesn't
>> really exist without a bit of help.
>>
>> 2. Please include changes to the relevant documentation (README + wiki)
>> so that people know to when and how to set MTD_VERSION. This may
>> prevent a few 'RTFM' e-mails.
>>
>
> Agreed for README. The wiki cannot be "patched" like this. We can
> Markus only make promise that he will update the information there,
> too.
>
>
>
Sounds good. Promises are fun.
regards,
Ben
next prev parent reply other threads:[~2007-11-27 22:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 16:46 [U-Boot-Users] [PATCH]: tools: fix fw_printenv tool to compile again Markus Klotzbücher
2007-11-26 17:04 ` Ben Warren
2007-11-26 22:19 ` Wolfgang Denk
2007-11-27 9:23 ` Markus Klotzbücher
2007-11-27 15:34 ` Ben Warren
2007-11-27 20:33 ` Markus Klotzbücher
2007-11-27 20:46 ` Ben Warren
2007-11-27 20:56 ` Jerry Van Baren
2007-11-27 22:12 ` Wolfgang Denk
2007-11-27 22:06 ` Wolfgang Denk
2007-11-27 22:30 ` Ben Warren [this message]
2008-01-09 7:51 ` Wolfgang Denk
2008-01-09 15:19 ` 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=474C9A6B.7000607@qstreams.com \
--to=bwarren@qstreams.com \
--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