From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: trouble compiling dwalker's for-next tree
Date: Sun, 10 Jan 2010 07:19:05 -0800 [thread overview]
Message-ID: <1263136745.2446.13.camel@desktop> (raw)
In-Reply-To: <20100109085106.GA23290@elf.ucw.cz>
On Sat, 2010-01-09 at 09:51 +0100, Pavel Machek wrote:
> Hi!
>
> It is great to have all changes merged, but I ran into some trouble:
>
> 1) mmc.h was missing.
>
> 2) CC arch/arm/mach-msm/rpc_hsusb.o
> arch/arm/mach-msm/rpc_hsusb.c: In function 'msm_chg_rpc_connect':
> arch/arm/mach-msm/rpc_hsusb.c:156: error: implicit declaration of
> function 'machine_is_msm7201a_surf'
> arch/arm/mach-msm/rpc_hsusb.c:156: error: implicit declaration of
> function 'machine_is_msm7x27_surf'
> arch/arm/mach-msm/rpc_hsusb.c:157: error: implicit declaration of
> function 'machine_is_qsd8x50_surf'
> make[1]: *** [arch/arm/mach-msm/rpc_hsusb.o] Error 1
>
> (I provided missing inlines)
>
> 3) CC arch/arm/mach-msm/acpuclock.o
> arch/arm/mach-msm/acpuclock.c:31:35: error: linux/remote_spinlock.h:
> No such file or directory
> arch/arm/mach-msm/acpuclock.c:106: error: expected '=', ',', ';',
> 'asm' or '__attribute__' before 'pll_lock'
>
It's still really really un-cooked .. There's tons of compile failures
that still need to be cleanup .. Most of the targets aren't going to
compile without tuning the config some..
What config are you using? I can try to correct some of the compile
failure ..
Daniel
prev parent reply other threads:[~2010-01-10 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 8:51 trouble compiling dwalker's for-next tree Pavel Machek
2010-01-10 15:19 ` Daniel Walker [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=1263136745.2446.13.camel@desktop \
--to=dwalker@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).