From: "andrzej zaborowski" <balrog@zabor.org>
To: Brian Swetland <swetland@google.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: perseus2 build broken (tip of tree)
Date: Thu, 2 Mar 2006 11:39:28 +0100 [thread overview]
Message-ID: <fb249edb0603020239i49571e2dj@mail.gmail.com> (raw)
In-Reply-To: <20060301225854.GA6223@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
On 01/03/06, Brian Swetland <swetland@google.com> wrote:
>
> Does anyone know if there's a simple fix for this...
> I can comment out mcbsp.o in the makefile and everything builds happily:
Yep, the simple fix would be to add the missing definitions in
include/asm-arm/arch-omap/mcbsp.h -- probably add "||
defined(CONFIG_ARCH_OMAP73)" at the end of line 43. A more correct
approach was discussed on this list some time ago.
Regards,
Andrew
--
balrog 2oo6
Dear Outlook users: Please remove me from your address books
http://www.newsforge.com/article.pl?sid=03/08/21/143258
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2006-03-02 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 22:58 perseus2 build broken (tip of tree) Brian Swetland
2006-03-02 10:39 ` andrzej zaborowski [this message]
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=fb249edb0603020239i49571e2dj@mail.gmail.com \
--to=balrog@zabor.org \
--cc=balrogg@gmail.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=swetland@google.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 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.