From: david.hagood@gmail.com
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Git as of 13-Jan-2009 build fail on OMAP3
Date: Tue, 13 Jan 2009 11:45:01 -0600 (CST) [thread overview]
Message-ID: <1abb5d601cc91bdaa406e206cb92094f.squirrel@localhost> (raw)
In-Reply-To: <20090113123056.GA2464@deprecation.cyrius.com>
I am attempting to build the stock kernel as pulled from the kernel GIT
server for an OMAP3 platform, and am getting errors.
The version I am working with (as displayed by "git show") is "commit
e0b325d310a6b11f1538413fd557d2eb98f2fae5".
The error is:
CC arch/arm/mach-omap2/board-omap3beagle.o
arch/arm/mach-omap2/board-omap3beagle.c: In function ‘beagle_twl_gpio_setup’:
arch/arm/mach-omap2/board-omap3beagle.c:132: error: ‘TWL4030_GPIO_MAX’
undeclared (first use in this function)
arch/arm/mach-omap2/board-omap3beagle.c:132: error: (Each undeclared
identifier is reported only once
arch/arm/mach-omap2/board-omap3beagle.c:132: error: for each function it
appears in.)
arch/arm/mach-omap2/board-omap3beagle.c: At top level:
arch/arm/mach-omap2/board-omap3beagle.c:141: error: variable
‘beagle_gpio_data’ has initializer but incomplete type
arch/arm/mach-omap2/board-omap3beagle.c:142: error: unknown field
‘gpio_base’ specified in initializer
arch/arm/mach-omap2/board-omap3beagle.c:142: warning: excess elements in
struct initializer
arch/arm/mach-omap2/board-omap3beagle.c:142: warning: (near initialization
for ‘beagle_gpio_data’)
arch/arm/mach-omap2/board-omap3beagle.c:143: error: unknown field
‘irq_base’ specified in initializer
arch/arm/mach-omap2/board-omap3beagle.c:143: warning: excess elements in
struct initializer
arch/arm/mach-omap2/board-omap3beagle.c:143: warning: (near initialization
for ‘beagle_gpio_data’)
arch/arm/mach-omap2/board-omap3beagle.c:144: error: unknown field
‘irq_end’ specified in initializer
arch/arm/mach-omap2/board-omap3beagle.c:144: warning: excess elements in
struct initializer
arch/arm/mach-omap2/board-omap3beagle.c:144: warning: (near initialization
for ‘beagle_gpio_data’)
arch/arm/mach-omap2/board-omap3beagle.c:145: error: unknown field
‘use_leds’ specified in initializer
arch/arm/mach-omap2/board-omap3beagle.c:145: warning: excess elements in
struct initializer
arch/arm/mach-omap2/board-omap3beagle.c:145: warning: (near initialization
for ‘beagle_gpio_data’)
arch/arm/mach-omap2/board-omap3beagle.c:146: error: unknown field
‘pullups’ specified in initializer
arch/arm/mach-omap2/board-omap3beagle.c:146: warning: excess elements in
struct initializer
arch/arm/mach-omap2/board-omap3beagle.c:146: warning: (near initialization
for ‘beagle_gpio_data’)
arch/arm/mach-omap2/board-omap3beagle.c:147: error: unknown field
‘pulldowns’ specified in initializer
arch/arm/mach-omap2/board-omap3beagle.c:148: warning: excess elements in
struct initializer
arch/arm/mach-omap2/board-omap3beagle.c:148: warning: (near initialization
for ‘beagle_gpio_data’)
arch/arm/mach-omap2/board-omap3beagle.c:149: error: unknown field ‘setup’
specified in initializer
arch/arm/mach-omap2/board-omap3beagle.c:149: warning: excess elements in
struct initializer
arch/arm/mach-omap2/board-omap3beagle.c:149: warning: (near initialization
for ‘beagle_gpio_data’)
arch/arm/mach-omap2/board-omap3beagle.c:152: error: variable
‘beagle_twldata’ has initializer but incomplete type
arch/arm/mach-omap2/board-omap3beagle.c:153: error: unknown field
‘irq_base’ specified in initializer
arch/arm/mach-omap2/board-omap3beagle.c:153: warning: excess elements in
struct initializer
arch/arm/mach-omap2/board-omap3beagle.c:153: warning: (near initialization
for ‘beagle_twldata’)
arch/arm/mach-omap2/board-omap3beagle.c:154: error: unknown field
‘irq_end’ specified in initializer
arch/arm/mach-omap2/board-omap3beagle.c:154: warning: excess elements in
struct initializer
arch/arm/mach-omap2/board-omap3beagle.c:154: warning: (near initialization
for ‘beagle_twldata’)
arch/arm/mach-omap2/board-omap3beagle.c:157: error: unknown field ‘gpio’
specified in initializer
arch/arm/mach-omap2/board-omap3beagle.c:157: warning: excess elements in
struct initializer
arch/arm/mach-omap2/board-omap3beagle.c:157: warning: (near initialization
for ‘beagle_twldata’)
arch/arm/mach-omap2/board-omap3beagle.c: In function ‘omap3_beagle_init’:
arch/arm/mach-omap2/board-omap3beagle.c:308: error: ‘gpio’ undeclared
(first use in this function)
make[1]: *** [arch/arm/mach-omap2/board-omap3beagle.o] Error 1
make: *** [arch/arm/mach-omap2] Error 2
I do have the TWL4030 enabled in the config.
Has anybody else tried this?
next prev parent reply other threads:[~2009-01-13 17:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 12:56 [2.6.28] Kernel panic after closing lid on HP 2510p Frans Pop
2009-01-13 12:30 ` Martin Michlmayr
2009-01-13 17:45 ` david.hagood [this message]
2009-01-14 15:55 ` Git as of 13-Jan-2009 build fail on OMAP3 Tony Lindgren
2009-01-13 19:31 ` [2.6.28] Kernel panic after closing lid on HP 2510p Frans Pop
2009-01-15 0:26 ` Andrew Morton
2009-01-15 2:03 ` Matthew Garrett
2009-01-15 2:15 ` Andrew Morton
2009-01-15 2:21 ` Matthew Garrett
2009-01-15 2:55 ` Zhang Rui
2009-01-15 2:55 ` Zhang Rui
2009-01-15 2:59 ` Matthew Garrett
2009-01-15 2:59 ` Matthew Garrett
2009-01-15 4:20 ` Wu Fengguang
2009-01-15 4:20 ` Wu Fengguang
2009-01-15 7:41 ` Martin Michlmayr
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=1abb5d601cc91bdaa406e206cb92094f.squirrel@localhost \
--to=david.hagood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.