All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 367] New: linux kernel compile error for arm926t
Date: Mon,  1 Jun 2009 08:04:57 +0000 (UTC)	[thread overview]
Message-ID: <bug-367-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=367

              Host: Debian 5.01
            Target: arm-linux-uclibcgnueabi
           Summary: linux kernel compile error for arm926t
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: alex_dobrynin at hotmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


In buildroot-2009.05-rc3 and internal toolchain
I get an error while compiling linux kernel (2.6.28):
  CC      arch/arm/kernel/traps.o
{standard input}: Assembler messages:
{standard input}:1094: Error: selected processor does not support `pld [r6,#0]'

It turns out that buildroot sets --with-arch=armv4t in gcc config
for target arm and variant arm926t.
Changing target/Config.in.arch to:
        default armv4t          if BR2_arm920t
        default armv4t          if BR2_arm922t
-       default armv4t          if BR2_arm926t
+       default armv5te         if BR2_arm926t
        default armv5t          if BR2_arm10t
        default armv6j          if BR2_arm1136jf_s
fixes the problem.


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2009-06-01  8:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01  8:04 bugzilla at busybox.net [this message]
2009-06-01  8:48 ` [Buildroot] [Bug 367] linux kernel compile error for arm926t bugzilla at busybox.net

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=bug-367-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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.