All of lore.kernel.org
 help / color / mirror / Atom feed
From: John David Anglin <dave.anglin@bell.net>
To: Graham Gower <graham.gower@gmail.com>
Cc: linux-parisc@vger.kernel.org
Subject: Re: failure to link kernel 3.0.3 with cross binutils-2.21.1/gcc-4.6.1
Date: Tue, 13 Sep 2011 09:55:37 -0400	[thread overview]
Message-ID: <4E6F60D9.5030203@bell.net> (raw)
In-Reply-To: <CAFk90B8F17-o3HqRGygu8OUb-Ncurqi-Ui+_u9kfaqmQG5nK4Q@mail.gmail.com>

On 9/13/2011 3:20 AM, Graham Gower wrote:
> /tmp/hppa64/bin/hppa64-linux-ld:
> arch/parisc/mm/built-in.o(.init.text+0xed0): cannot reach
> flush_tlb_all_local
> /tmp/hppa64/bin/hppa64-linux-ld: BFD (GNU Binutils) 2.21.1 internal
> error, aborting at ../../binutils-2.21.1/bfd/elf64-hppa.c line 3956 in
> elf64_hppa_relocate_section
>
> Any clues?
Check the relocation at arch/parisc/mm/built-in.o(.init.text+0xed0) with 
readelf
or objdump.  It should be R_PARISC_PCREL22F.  If this isn't a 22-bit branch,
then the call needs changing (e.g., change a bl to b,l).

If this is a 22-bit call, then you will have to remove some stuff from 
your .config.
Maybe use more modules.

The hppa64 linker doesn't have stub support  for long calls.  The maximum
branch distance (R_PARISC_PCREL22F) is 8388608 bytes.

Stub support could be added to hppa64 in a manner similar to that for 
hppa32,
but there isn't a 64-bit userspace except on HP-UX.  On HP-UX, the HP linker
is better.  I made a number of changes a few years ago to make this possible
but there's still quite a bit of work involved.

Dave

-- 
John David Anglin    dave.anglin@bell.net


  parent reply	other threads:[~2011-09-13 13:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-13  7:20 failure to link kernel 3.0.3 with cross binutils-2.21.1/gcc-4.6.1 Graham Gower
2011-09-13  7:48 ` Rolf Eike Beer
2011-09-13 14:03   ` John David Anglin
2011-09-13 13:55 ` John David Anglin [this message]
2011-09-14  1:44   ` Graham Gower

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=4E6F60D9.5030203@bell.net \
    --to=dave.anglin@bell.net \
    --cc=graham.gower@gmail.com \
    --cc=linux-parisc@vger.kernel.org \
    /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.