From: Colin Watson <cjwatson@ubuntu.com>
To: grub-devel@gnu.org
Subject: Re: mips-arc build failure on xz_decompress.img
Date: Tue, 23 Sep 2014 16:49:33 +0100 [thread overview]
Message-ID: <20140923154933.GA850@riva.ucam.org> (raw)
In-Reply-To: <541EF452.7090000@gmail.com>
On Sun, Sep 21, 2014 at 05:52:50PM +0200, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> @Colin: do you have intermediate files? We should probably strip those
> extra sections.
Right, I'm seeing the same thing on mipsel now, so it looks like a
change introduced by new binutils. I've attached xz_decompress.image.
"objdump -h" from a build on Debian wheezy looks like this:
obj/grub-yeeloong/grub-core/xz_decompress.image: file format elf32-tradlittlemips
Sections:
Idx Name Size VMA LMA File off Algn
0 .text 00002ab0 80100000 80100000 000000b0 2**4
CONTENTS, ALLOC, LOAD, CODE
1 .reginfo 00000018 00400094 00400094 00000094 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA, LINK_ONCE_SAME_SIZE
2 .rodata 000000dc 80102ab0 80102ab0 00002b60 2**4
CONTENTS, ALLOC, LOAD, READONLY, DATA
3 .data 00000010 80102b90 80102b90 00002c40 2**4
CONTENTS, ALLOC, LOAD, DATA
4 .sbss 00000004 80102ba0 80102ba0 00002c50 2**2
ALLOC
5 .bss 00007408 80102bb0 80102bb0 00002c50 2**4
ALLOC
6 .comment 0000001c 00000000 00000000 00002c50 2**0
CONTENTS, READONLY
7 .pdr 000002e0 00000000 00000000 00002c6c 2**2
CONTENTS, READONLY
8 .gnu.attributes 00000010 00000000 00000000 00002f4c 2**0
CONTENTS, READONLY
9 .mdebug.abi32 00000000 00000000 00000000 00002f5c 2**0
CONTENTS, READONLY
And "objdump -h" from a build on Debian jessie looks like this:
obj/grub-yeeloong/grub-core/xz_decompress.image: file format elf32-tradlittlemips
Sections:
Idx Name Size VMA LMA File off Algn
0 .text 00002af0 80100000 80100000 000000f0 2**4
CONTENTS, ALLOC, LOAD, CODE
1 .MIPS.abiflags 00000018 004000b8 004000b8 000000b8 2**3
CONTENTS, ALLOC, LOAD, READONLY, DATA, LINK_ONCE_SAME_SIZE
2 .reginfo 00000018 004000d0 004000d0 000000d0 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA, LINK_ONCE_SAME_SIZE
3 .rodata 0000007c 80102af0 80102af0 00002be0 2**4
CONTENTS, ALLOC, LOAD, READONLY, DATA
4 .data.rel.ro 00000058 80102b6c 80102b6c 00002c5c 2**2
CONTENTS, ALLOC, LOAD, DATA
5 .data 00000010 80102bd0 80102bd0 00002cc0 2**4
CONTENTS, ALLOC, LOAD, DATA
6 .got 00000044 80102be0 80102be0 00002cd0 2**4
CONTENTS, ALLOC, LOAD, DATA
7 .sbss 00000004 80102c24 80102c24 00002d14 2**2
ALLOC
8 .bss 00007408 80102c30 80102c30 00002d14 2**4
ALLOC
9 .comment 0000001d 00000000 00000000 00002d14 2**0
CONTENTS, READONLY
10 .pdr 000002e0 00000000 00000000 00002d34 2**2
CONTENTS, READONLY
11 .gnu.attributes 00000010 00000000 00000000 00003014 2**0
CONTENTS, READONLY
12 .mdebug.abi32 00000000 00000000 00000000 00003024 2**0
CONTENTS, READONLY
"-R .MIPS.abiflags" seems to fix things; does that need to be added
anywhere other than gentpl.py:image?
--
Colin Watson [cjwatson@ubuntu.com]
prev parent reply other threads:[~2014-09-23 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 22:29 mips-arc build failure on xz_decompress.img Colin Watson
2014-08-26 4:52 ` Andrei Borzenkov
2014-08-26 8:23 ` Andrei Borzenkov
2014-09-21 15:52 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-09-23 15:49 ` Colin Watson [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=20140923154933.GA850@riva.ucam.org \
--to=cjwatson@ubuntu.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).