From: Nathan Pilatzke <nathanpilatzke@gmail•com>
To: "H. Peter Anvin" <hpa@zytor•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 13:34:14 -0400 [thread overview]
Message-ID: <447DD396.8070603@gmail.com> (raw)
In-Reply-To: <447DC91D.8010508@zytor.com>
Applied the patch, did a 'make clean' and 'make'. The patch had no
effect for me, exact same errors.
H. Peter Anvin wrote:
> 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
>
>
> ------------------------------------------------------------------------
>
> 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
prev parent reply other threads:[~2006-05-31 17:34 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
2006-05-31 17:34 ` Nathan Pilatzke [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=447DD396.8070603@gmail.com \
--to=nathanpilatzke@gmail$(echo .)com \
--cc=hpa@zytor$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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