From: Eino-Ville Talvala <talvala@stanford.edu>
To: Niamathullah sharief <omapsha@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: ARM CROSS COMPILATION
Date: Thu, 17 Dec 2009 22:37:58 -0800 [thread overview]
Message-ID: <4B2B2346.6000104@stanford.edu> (raw)
In-Reply-To: <4ad3b6300912172220v5d6af078n302284331cc4345a@mail.gmail.com>
On 12/17/2009 10:20 PM, Niamathullah sharief wrote:
> Hello,
> I am trying to compile my kernel for ARM Processor. when i do that i
> am getting some following error. I didnt find what will be the
> problem.
>
>
Hi,
> root@ariem-desktop:/home/ariem/Desktop/kernels/linux-2.6.28-006rc8#
> make CROSS_COMPILE=/home/ariem/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-
> uImage
> CHK include/linux/version.h
> make[1]: `include/asm-arm/mach-types.h' is up to date.
> CHK include/linux/utsrelease.h
> SYMLINK include/asm -> include/asm-arm
> CALL scripts/checksyscalls.sh
> <stdin>:1097:2: warning: #warning syscall fadvise64 not implemented
> <stdin>:1265:2: warning: #warning syscall migrate_pages not implemented
> <stdin>:1321:2: warning: #warning syscall pselect6 not implemented
> <stdin>:1325:2: warning: #warning syscall ppoll not implemented
> <stdin>:1365:2: warning: #warning syscall epoll_pwait not implemented
> CC init/main.o
> /tmp/cczCT0T5.s: Assembler messages:
> /tmp/cczCT0T5.s:255: Error: selected processor does not support `cpsie i'
> /tmp/cczCT0T5.s:704: Error: selected processor does not support `cpsid i'
> /tmp/cczCT0T5.s:712: Error: selected processor does not support `cpsid i'
> /tmp/cczCT0T5.s:726: Error: selected processor does not support `cpsid i'
> /tmp/cczCT0T5.s:740: Error: selected processor does not support `cpsid i'
> /tmp/cczCT0T5.s:812: Error: selected processor does not support `cpsid i'
> /tmp/cczCT0T5.s:837: Error: selected processor does not support `cpsie i'
> make[1]: *** [init/main.o] Error 1
> make: *** [init] Error 2
> root@ariem-desktop:/home/ariem/Desktop/kernels/linux-2.6.28-006rc8#
>
> Kindly help me
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Unless you're using an OMAP-based ARM processor, this is probably not
the right list to be asking this. You're also not giving sufficient
information for anyone to help you much - what processor and what
hardware platform are you compiling for?
In any case, have you run the proper defconfig for your board - see, for
example, the discussion below:
http://linux.omap.com/pipermail/linux-omap-open-source/2007-August/010792.html
Good luck!
Eino-Ville Talvala
Computer Graphics Lab
Stanford University
prev parent reply other threads:[~2009-12-18 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 6:20 ARM CROSS COMPILATION Niamathullah sharief
2009-12-18 6:37 ` Eino-Ville Talvala [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=4B2B2346.6000104@stanford.edu \
--to=talvala@stanford.edu \
--cc=linux-omap@vger.kernel.org \
--cc=omapsha@gmail.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