From: "H. Peter Anvin" <hpa@zytor.com>
To: Nathan Pilatzke <nathanpilatzke@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: >=2.6.17-rc4-mm1 kernel compilation problem (relocation truncated to fit)
Date: Wed, 31 May 2006 09:49:33 -0700 [thread overview]
Message-ID: <447DC91D.8010508@zytor.com> (raw)
In-Reply-To: <447DAAE4.7010503@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
Nathan Pilatzke wrote:
> I am getting compilation errors for 2.6.17-rc5-mm1 all the way back to
> 2.6.17-rc4-mm1. Kernel 2.6.17-rc3-mm1 compiles better for me (I get the
> undefined reference to __udivdi3 error that has been reported
> previously). Here are the errors that I get for 2.6.17-rc5-mm1:
>
Could you try the following patch?
-hpa
[-- Attachment #2: ppc32.so.address --]
[-- Type: text/plain, Size: 758 bytes --]
diff --git a/usr/klibc/arch/ppc/MCONFIG b/usr/klibc/arch/ppc/MCONFIG
index 8b51e65..e101453 100644
--- a/usr/klibc/arch/ppc/MCONFIG
+++ b/usr/klibc/arch/ppc/MCONFIG
@@ -13,9 +13,9 @@ KLIBCBITSIZE = 32
# Extra linkflags when building the shared version of the library
# This address needs to be reachable using normal inter-module
# calls, and work on the memory models for this architecture
-# 256-16 MB - normal binaries start at 256 MB, and jumps are limited
+# 256-8 MB - normal binaries start at 256 MB, and jumps are limited
# to +/- 16 MB
-KLIBCSHAREDFLAGS = -Ttext 0x0f000200
+KLIBCSHAREDFLAGS = -Ttext 0x0f800200
# The kernel so far has both asm-ppc* and asm-powerpc.
KLIBCARCHINCFLAGS = -I$(KLIBCKERNELOBJ)arch/$(KLIBCARCH)/include
next prev parent reply other threads:[~2006-05-31 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 14:40 >=2.6.17-rc4-mm1 kernel compilation problem (relocation truncated to fit) Nathan Pilatzke
2006-05-31 16:49 ` H. Peter Anvin [this message]
2006-05-31 17:34 ` Nathan Pilatzke
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=447DC91D.8010508@zytor.com \
--to=hpa@zytor.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=nathanpilatzke@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 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.