From: Timur Tabi <timur@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>,
PowerPC dev list <linuxppc-dev@ozlabs.org>
Subject: include/asm/cpm2.h:14:21: error: asm/cpm.h: No such file or directory
Date: Thu, 04 Oct 2007 17:28:42 -0500 [thread overview]
Message-ID: <4705691A.9020509@freescale.com> (raw)
Kumar, this is what I get when I compile your 2.6.24 branch for the 8610:
CC arch/powerpc/sysdev/fsl_soc.o
In file included from arch/powerpc/sysdev/fsl_soc.c:40:
include/asm/cpm2.h:14:21: error: asm/cpm.h: No such file or directory
make[1]: *** [arch/powerpc/sysdev/fsl_soc.o] Error 1
make: *** [arch/powerpc/sysdev] Error 2
Commenting out the "#include <asm/cpm.h>" in cpm2.h makes the compilation
failure go away, but I don't know if that's the proper fix, since the 8610
doesn't have a CPM.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next reply other threads:[~2007-10-04 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 22:28 Timur Tabi [this message]
2007-10-05 0:57 ` include/asm/cpm2.h:14:21: error: asm/cpm.h: No such file or directory Kumar Gala
2007-10-08 4:36 ` Misbah khan
2007-10-10 4:03 ` Misbah khan
2007-10-10 16:39 ` Scott Wood
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=4705691A.9020509@freescale.com \
--to=timur@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).