From: Olliver Schinagl <oliver+list@schinagl.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] Compiling u-boot (sunxi/next)
Date: Fri, 18 Sep 2015 10:22:58 +0200 [thread overview]
Message-ID: <55FBC9E2.7070400@schinagl.nl> (raw)
Hey all,
just working on a _defconfig for our board and noticed that u-boot fails
to compile if my defconfig doesn't have:
# CONFIG_CMD_IMLS is not set
What supprised me is that it has to be in there as a comment to unset
it. I would have imaged that it would be unset by default and only be
available if set in the defconfig, or rather, how can commenting it in
the defconfig unset it?
I've added the u-boot list to the CC, but afaik it's not an open list
and my registrations have failed on a number of occasions ...
Not that it should fail to compile either way, here's the output:
In file included from
/home/oliver/Ultimaker/dev/sunxi-bsp/u-boot-sunxi/common/cmd_bootm.c:35:0:
/home/oliver/Ultimaker/dev/sunxi-bsp/u-boot-sunxi/include/mtd/cfi_flash.h:168:22:
error: unknown type name ?flash_info_t?
void flash_write_cmd(flash_info_t * info, flash_sect_t sect,
^
/home/oliver/Ultimaker/dev/sunxi-bsp/u-boot-sunxi/include/mtd/cfi_flash.h:168:43:
error: unknown type name ?flash_sect_t?
void flash_write_cmd(flash_info_t * info, flash_sect_t sect,
^
/home/oliver/Ultimaker/dev/sunxi-bsp/u-boot-sunxi/include/mtd/cfi_flash.h:172:22:
error: unknown type name ?flash_info_t?
void flash_cmd_reset(flash_info_t *info);
^
/home/oliver/Ultimaker/dev/sunxi-bsp/u-boot-sunxi/common/cmd_bootm.c:36:8:
error: unknown type name ?flash_info_t?
extern flash_info_t flash_info[]; /* info for FLASH chips */
^
/home/oliver/Ultimaker/dev/sunxi-bsp/u-boot-sunxi/common/cmd_bootm.c: In
function ?do_imls_nor?:
/home/oliver/Ultimaker/dev/sunxi-bsp/u-boot-sunxi/common/cmd_bootm.c:321:2:
error: unknown type name ?flash_info_t?
flash_info_t *info;
^
/home/oliver/Ultimaker/dev/sunxi-bsp/u-boot-sunxi/common/cmd_bootm.c:326:7:
error: ?CONFIG_SYS_MAX_FLASH_BANKS? undeclared (first use in this function)
i < CONFIG_SYS_MAX_FLASH_BANKS; ++i, ++info) {
^
/home/oliver/Ultimaker/dev/sunxi-bsp/u-boot-sunxi/common/cmd_bootm.c:326:7:
note: each undeclared identifier is reported only once for each function
it appears in
/home/oliver/Ultimaker/dev/sunxi-bsp/u-boot-sunxi/common/cmd_bootm.c:328:11:
error: request for member ?flash_id? in something not a structure or union
if (info->flash_id == FLASH_UNKNOWN)
^
/home/oliver/Ultimaker/dev/sunxi-bsp/u-boot-sunxi/common/cmd_bootm.c:328:25:
error: ?FLASH_UNKNOWN? undeclared (first use in this function)
if (info->flash_id == FLASH_UNKNOWN)
^
/home/oliver/Ultimaker/dev/sunxi-bsp/u-boot-sunxi/common/cmd_bootm.c:330:23:
error: request for member ?sector_count? in something not a structure or
union
for (j = 0; j < info->sector_count; ++j) {
^
/home/oliver/Ultimaker/dev/sunxi-bsp/u-boot-sunxi/common/cmd_bootm.c:332:22:
error: request for member ?start? in something not a structure or union
hdr = (void *)info->start[j];
Olliver
next reply other threads:[~2015-09-18 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 8:22 Olliver Schinagl [this message]
2015-09-18 8:32 ` [U-Boot] Compiling u-boot (sunxi/next) Ian Campbell
2015-09-18 8:38 ` Olliver Schinagl
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=55FBC9E2.7070400@schinagl.nl \
--to=oliver+list@schinagl.nl \
--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