From: "Loïc Minier" <lool@dooz.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] kfreebsd build failure - fw_env.c:43:27: error: mtd/mtd-user.h: No such file or directory
Date: Mon, 7 Feb 2011 22:09:00 +0100 [thread overview]
Message-ID: <20110207210900.GA5848@bee.dooz.org> (raw)
Hey
"make tools-all" fails under Debian kfreebsd-amd64 and -i386 due to the
lack of MTD headers:
make[2]: Entering directory `/build/buildd-u-boot_2010.12-2-kfreebsd-i386-yWW1BA/u-boot-2010.12/tools/env'
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -idirafter /build/buildd-u-boot_2010.12-2-kfreebsd-i386-yWW1BA/u-boot-2010.12/include -idirafter /build/buildd-u-boot_2010.12-2-kfreebsd-i386-yWW1BA/u-boot-2010.12/include2 -idirafter /build/buildd-u-boot_2010.12-2-kfreebsd-i386-yWW1BA/u-boot-2010.12/include -DUSE_HOSTCC -o fw_printenv crc32.c fw_env.c fw_env_main.c
fw_env.c:43:27: error: mtd/mtd-user.h: No such file or directory
[...]
https://buildd.debian.org/fetch.cgi?pkg=u-boot&arch=kfreebsd-i386&ver=2010.12-2&stamp=1295512921&file=log&as=raw
I didn't find any MTD header in the kfreebsd package.
Would someone know whether this is supposed to build under freebsd?
If not, does it make sense to ifdef out the MTD uses in fw_env.c? (I
think it's also possible to interact with real files containing the
environment.)
If not, I guess this should be removed from tools-all is mtd/mtd-user.h
isn't found; is there any recommendation in doing this?
Cheers,
--
Lo?c Minier
next reply other threads:[~2011-02-07 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 21:09 Loïc Minier [this message]
2011-02-07 22:06 ` [U-Boot] kfreebsd build failure - fw_env.c:43:27: error: mtd/mtd-user.h: No such file or directory Wolfgang Denk
2011-02-07 22:23 ` Loïc Minier
2011-02-07 23:23 ` [U-Boot] [PATCH] Only build fw_printenv if we have mtd/mtd-user.h Loïc Minier
2011-04-12 19:27 ` Wolfgang Denk
2011-04-12 19:46 ` Loïc Minier
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=20110207210900.GA5848@bee.dooz.org \
--to=lool@dooz.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