public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Pink Boy <dasfoo@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Problem building fw_printenv un u-boot 1.3.4
Date: Mon, 1 Dec 2008 19:03:19 -0800 (PST)	[thread overview]
Message-ID: <284633.10690.qm@web31801.mail.mud.yahoo.com> (raw)
In-Reply-To: <20081202002006.GA17288@crust.elkhashab.com>


Hi,

I'm back haxing at u-boot.  Specifically I'm trying to build 
fw_printenv so that I can use u-boots environment to store my
boards MAC address.

I've been able to build a u-boot that runs off of u-boot-1.3.4
for the AT91RM9200DK.  However when I try and build the utilities
to read and write the env I get the following error below.  Any
ideas why this is happening?

Matt
Tehama Wireless
---

# make env CROSS_COMPILE=armv4l-uclibc- MTD_VERSION=old 
make -C tools/env all MTD_VERSION=old || exit 1
make[1]: Entering directory `/home/tu/workspaces/uboot/u-boot-1.3.4/tools/env'
armv4l-uclibc-gcc -Wall -DUSE_HOSTCC -I/home/tu/workspaces/uboot/u-boot-1.3.4/include -DMTD_OLD crc32.c  fw_env.c  fw_env_main.c -o fw_printenv
In file included from /home/tu/workspaces/uboot/u-boot-1.3.4/include/linux/mtd/mtd.h:12,
                 from fw_env.c:36:
/home/tu/workspaces/uboot/u-boot-1.3.4/include/linux/mtd/mtd-abi.h:11: error: expected specifier-qualifier-list before ?uint32_t?
/home/tu/workspaces/uboot/u-boot-1.3.4/include/linux/mtd/mtd-abi.h:16: error: expected specifier-qualifier-list before ?uint32_t?
/home/tu/workspaces/uboot/u-boot-1.3.4/include/linux/mtd/mtd-abi.h:61: error: expected specifier-qualifier-list before ?uint8_t?
/home/tu/workspaces/uboot/u-boot-1.3.4/include/linux/mtd/mtd-abi.h:72: error: expected specifier-qualifier-list before ?uint32_t?
/home/tu/workspaces/uboot/u-boot-1.3.4/include/linux/mtd/mtd-abi.h:93: error: expected specifier-qualifier-list before ?uint32_t?
fw_env.c: In function ?fw_setenv?:
fw_env.c:386: error: ?uint8_t? undeclared (first use in this function)
fw_env.c:386: error: (Each undeclared identifier is reported only once
fw_env.c:386: error: for each function it appears in.)
fw_env.c:386: error: expected expression before ?)? token
fw_env.c:386: error: too few arguments to function ?crc32?
fw_env.c: In function ?flash_io?:
fw_env.c:400: error: ?erase_info_t? undeclared (first use in this function)
fw_env.c:400: error: expected ?;? before ?erase?
fw_env.c:431: error: ?erase? undeclared (first use in this function)
fw_env.c: In function ?env_init?:
fw_env.c:621: error: ?uint8_t? undeclared (first use in this function)
fw_env.c:621: error: expected expression before ?)? token
fw_env.c:621: error: too few arguments to function ?crc32?
fw_env.c:645: error: expected expression before ?)? token
fw_env.c:645: error: too few arguments to function ?crc32?
make[1]: *** [fw_printenv] Error 1
make[1]: Leaving directory `/home/tu/workspaces/uboot/u-boot-1.3.4/tools/env'
make: *** [env] Error 1
# 

  reply	other threads:[~2008-12-02  3:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02  0:20 [U-Boot] pci booting 460ex seems to hang at tlb entries Ayman M. El-Khashab
2008-12-02  3:03 ` Pink Boy [this message]
2008-12-03  1:38   ` [U-Boot] Problem building fw_printenv un u-boot 1.3.4 Pink Boy
2008-12-03 11:45     ` Wolfgang Denk
2008-12-03 21:08       ` Pink Boy

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=284633.10690.qm@web31801.mail.mud.yahoo.com \
    --to=dasfoo@yahoo.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