From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: aarch64: relocation 0x105 is not implemented yet.
Date: Sat, 28 Dec 2013 23:00:39 +0400 [thread overview]
Message-ID: <1388257239.918.92.camel@opensuse.site> (raw)
In-Reply-To: <1388252883.918.88.camel@opensuse.site>
[-- Attachment #1: Type: text/plain, Size: 3664 bytes --]
В Сб, 28/12/2013 в 21:48 +0400, Andrey Borzenkov пишет:
> В Сб, 28/12/2013 в 18:11 +0100, Vladimir 'φ-coder/phcoder' Serbinenko
> пишет:
> > On 27.12.2013 20:07, Andrey Borzenkov wrote:
> > > I tried to build RPM for aarch64; it fails building image with
> > >
> > > [ 1273s] + ./grub-mkimage -O arm64-efi -o grub.efi --prefix= -d
> > > grub-core all_video boot cat chain configfile echo efinet font gfxmenu
> > > gfxterm gzio halt iso9660 jpeg minicmd normal part_apple part_msdos
> > > part_gpt password_pbkdf2 png reboot search search_fs_uuid search_fs_file
> > > search_label sleep test video fat loadenv linux ext2 btrfs ext2 xfs jfs
> > > reiserfs efinet tftp mdraid09 mdraid1x lvm
> > > [ 1273s] ./grub-mkimage: error: relocation 0x105 is not implemented yet.
> > >
> > This shouldn't happen as those relocation assume 32-bit range. Is
> > -mcmodel=large properly passed?
>
> Looks like some files are compiled without it
>
> [ 992s] gcc -DHAVE_CONFIG_H -I. -I../../grub-core -I.. -Wall -W
> -I../../include -I../include -DGRUB_MACHINE_EFI=1
> -DGRUB_MACHINE=ARM64_EFI -nostdinc
> -isystem /usr/lib64/gcc/aarch64-suse-linux/4.8/include -DGRUB_FILE=
> \"lib/setjmp.S\" -I. -I../../grub-core -I.. -I../.. -I../../include
> -I../include -I../../grub-core/lib/libgcrypt-grub/src/ -g
> -DGRUB_FILE=\"lib/setjmp.S\" -I. -I../../grub-core -I.. -I../..
> -I../../include -I../include -I../../grub-core/lib/libgcrypt-grub/src/
> -DASM_FILE=1 -fno-strict-aliasing -fno-inline-functions-called-once
> -MT lib/setjmp_module-setjmp.o -MD -MP -MF
> lib/.deps-core/setjmp_module-setjmp.Tpo -c -o lib/setjmp_module-setjmp.o
> `test -f 'lib/setjmp.S' || echo '../../grub-core/'`lib/setjmp.S
>
> [ 1161s] gcc -DHAVE_CONFIG_H -I. -I../../grub-core -I.. -Wall -W
> -I../../include -I../include -DGRUB_MACHINE_EFI=1
> -DGRUB_MACHINE=ARM64_EFI -nostdinc
> -isystem /usr/lib64/gcc/aarch64-suse-linux/4.8/include -DGRUB_FILE=
> \"kern/arm64/efi/startup.S\" -I. -I../../grub-core -I.. -I../..
> -I../../include -I../include -I../../grub-core/lib/libgcrypt-grub/src/
> -DGRUB_KERNEL=1 -g -DGRUB_FILE=\"kern/arm64/efi/startup.S\" -I.
> -I../../grub-core -I.. -I../.. -I../../include -I../include
> -I../../grub-core/lib/libgcrypt-grub/src/ -DASM_FILE=1
> -fno-strict-aliasing -fno-inline-functions-called-once -MT
> kern/arm64/efi/kernel_exec-startup.o -MD -MP -MF
> kern/arm64/efi/.deps-core/kernel_exec-startup.Tpo -c -o
> kern/arm64/efi/kernel_exec-startup.o `test -f 'kern/arm64/efi/startup.S'
> || echo '../../grub-core/'`kern/arm64/efi/startup.S
>
> [ 1163s] gcc -DHAVE_CONFIG_H -I. -I../../grub-core -I.. -Wall -W
> -I../../include -I../include -DGRUB_MACHINE_EFI=1
> -DGRUB_MACHINE=ARM64_EFI -nostdinc
> -isystem /usr/lib64/gcc/aarch64-suse-linux/4.8/include -DGRUB_FILE=
> \"kern/arm64/cache_flush.S\" -I. -I../../grub-core -I.. -I../..
> -I../../include -I../include -I../../grub-core/lib/libgcrypt-grub/src/
> -DGRUB_KERNEL=1 -g -DGRUB_FILE=\"kern/arm64/cache_flush.S\" -I.
> -I../../grub-core -I.. -I../.. -I../../include -I../include
> -I../../grub-core/lib/libgcrypt-grub/src/ -DASM_FILE=1
> -fno-strict-aliasing -fno-inline-functions-called-once -MT
> kern/arm64/kernel_exec-cache_flush.o -MD -MP -MF
> kern/arm64/.deps-core/kernel_exec-cache_flush.Tpo -c -o
> kern/arm64/kernel_exec-cache_flush.o `test -f 'kern/arm64/cache_flush.S'
> || echo '../../grub-core/'`kern/arm64/cache_flush.S
>
>
Still the same even after adding -mcmodel=large to CCASFLAGS. Is it
possible that compiler generates small relocation where appropriate even
with -mcmodel=large?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-12-28 19:01 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 [this message]
2013-12-29 1:55 ` Leif Lindholm
2013-12-29 5:24 ` Andrey Borzenkov
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=1388257239.918.92.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 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.