From: Brian Swetland <swetland@google.com>
To: linux-omap-open-source@linux.omap.com
Subject: perseus2 build broken (tip of tree)
Date: Wed, 1 Mar 2006 14:58:54 -0800 [thread overview]
Message-ID: <20060301225854.GA6223@localhost.localdomain> (raw)
Does anyone know if there's a simple fix for this...
I can comment out mcbsp.o in the makefile and everything builds happily:
arch/arm/plat-omap/mcbsp.c:67: error: `OMAP_MAX_MCBSP_COUNT' undeclared
here (not in a function)
arch/arm/plat-omap/mcbsp.c: In function `omap_mcbsp_config':
arch/arm/plat-omap/mcbsp.c:162: error: `OMAP_MCBSP_REG_SPCR2' undeclared
(first use in this function)
arch/arm/plat-omap/mcbsp.c:162: error: (Each undeclared identifier is
reported only once
arch/arm/plat-omap/mcbsp.c:162: error: for each function it appears in.)
arch/arm/plat-omap/mcbsp.c:163: error: `OMAP_MCBSP_REG_SPCR1' undeclared
(first use in this function)
...
It looks like at some point either mcbsp stopped being optional
or it was changed so it doesn't build on ARCH_OMAP730.
Brian
next reply other threads:[~2006-03-01 22:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 22:58 Brian Swetland [this message]
2006-03-02 10:39 ` perseus2 build broken (tip of tree) andrzej zaborowski
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=20060301225854.GA6223@localhost.localdomain \
--to=swetland@google.com \
--cc=linux-omap-open-source@linux.omap.com \
/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