Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1231] New: (sparc) Linux kernel fails to build
Date: Wed,  3 Mar 2010 00:13:32 +0000 (UTC)	[thread overview]
Message-ID: <bug-1231-163@https.bugs.busybox.net/> (raw)

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

              Host: x86_64
            Target: sparc
             Build: 2010.02
           Summary: (sparc) Linux kernel fails to build
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: thedukevip at gmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Hello,
I'm using buildroot 2010.02, configure it for sparc (not sparc64), also the
kernel is properly configured (sparc)
after make, (or make linux26, after building the toolchain etc) I get the
followin error in the last stage of kernel building !!

  LD      vmlinux
  SYSMAP  System.map
  SYSMAP  .tmp_System.map
  BTFIX   arch/sparc/boot/btfix.S
  AS      arch/sparc/boot/btfix.o
  LD      arch/sparc/boot/image
arch/sparc/kernel/head_32.o: In function `current_pc':
(.head.text+0xc040): relocation truncated to fit: R_SPARC_WDISP22 against
`.init.text'
arch/sparc/kernel/built-in.o:(.fixup+0x4): relocation truncated to fit:
R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/built-in.o:(.fixup+0xc): relocation truncated to fit:
R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/built-in.o:(.fixup+0x14): relocation truncated to fit:
R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/built-in.o:(.fixup+0x1c): relocation truncated to fit:
R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/built-in.o:(.fixup+0x28): relocation truncated to fit:
R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/built-in.o:(.fixup+0x30): relocation truncated to fit:
R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/built-in.o:(.fixup+0x38): relocation truncated to fit:
R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/built-in.o:(.fixup+0x40): relocation truncated to fit:
R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/built-in.o:(.fixup+0x48): relocation truncated to fit:
R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/built-in.o:(.fixup+0x50): additional relocation overflows
omitted from the output
make[2]: *** [arch/sparc/boot/image] Error 1
make[1]: *** [zImage] Error 2
make[1]: Leaving directory
`/media/Data/PFE/buildroot/output/build/linux-2.6.32.9'
make: ***
[/media/Data/PFE/buildroot/output/build/linux-2.6.32.9/arch/sparc/boot/zImage]
Error 2

Any help ?! At least a useful debugging method !


-- 
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:[~2010-03-03  0:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03  0:13 bugzilla at busybox.net [this message]
2010-04-09 14:54 ` [Buildroot] [Bug 1231] (sparc) Linux kernel fails to build bugzilla at busybox.net
2010-07-18 19:43 ` bugzilla at busybox.net
2010-07-26 14:44 ` 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-1231-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox