grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: aarch64: relocation 0x105 is not implemented yet.
Date: Sun, 29 Dec 2013 09:24:04 +0400	[thread overview]
Message-ID: <1388294644.918.99.camel@opensuse.site> (raw)
In-Reply-To: <CAF7UmSxjGcM5EQ8emMAaoQ8f_Cb7Qrf51k5vkuQzAWS0Sj8qkg@mail.gmail.com>

В Вс, 29/12/2013 в 01:55 +0000, Leif Lindholm пишет:
> It shouldn't, but difficult to say without knowing more details.
> Can you run the mkimage with -v and pinpoint the triggering module?
> 

This comes from .eh_frame section and fails for kernel.exec already. 

RELOCATION RECORDS FOR [.eh_frame]:
OFFSET           TYPE              VALUE 
000000000000001c R_AARCH64_PREL32  .text+0x0000000000009b70
0000000000000044 R_AARCH64_PREL32  .text+0x0000000000009b78

Also there are ABS32 relocations in various .debug_* sections but I
presume they are handled by --strip-unneeded.



  reply	other threads:[~2013-12-29  5:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-27 19:07 aarch64: relocation 0x105 is not implemented yet Andrey Borzenkov
2013-12-28 17:11 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-28 17:48   ` Andrey Borzenkov
2013-12-28 19:00     ` Andrey Borzenkov
2013-12-29  1:55       ` Leif Lindholm
2013-12-29  5:24         ` Andrey Borzenkov [this message]
2013-12-29 12:44           ` Leif Lindholm
2013-12-29 13:06             ` Andrey Borzenkov
2013-12-29 13:06             ` Leif Lindholm
2013-12-29 13:09               ` Leif Lindholm
2013-12-29 14:01                 ` Andrey Borzenkov
2013-12-29 14:07                   ` Leif Lindholm
2013-12-29 18:12                   ` Leif Lindholm
2013-12-29 19:03                     ` Andrey Borzenkov
2013-12-30  0:40                       ` Leif Lindholm
2013-12-30  2:45                         ` Andrey Borzenkov
2013-12-30 12:43                           ` Leif Lindholm
2013-12-30 13:15                   ` Leif Lindholm

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=1388294644.918.99.camel@opensuse.site \
    --to=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).