From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: mips-arc build failure on xz_decompress.img
Date: Tue, 26 Aug 2014 12:23:31 +0400 [thread overview]
Message-ID: <CAA91j0Xg2SmzjKctNXZ7B6objYqM49L8RVp0FLerL+ix1Nji=g@mail.gmail.com> (raw)
In-Reply-To: <CAA91j0VwwNrjc4Tjzyx=NUqyXU0-AJge_FEeLiPMWk4auy2utw@mail.gmail.com>
On Tue, Aug 26, 2014 at 8:52 AM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
> On Tue, Aug 26, 2014 at 2:29 AM, Colin Watson <cjwatson@ubuntu.com> wrote:
>> I tried to enable the mips-arc platform in Debian. When test-building,
>> I first ran into a GCC uninitialised warning (promoted to an error by
>> -Werror), which I fixed in
>> http://git.savannah.gnu.org/gitweb/?p=grub.git;a=commitdiff;h=1de3a48098053aaebd35232bd73e3ce3f3fdf51c.
>> Following that, I get:
>>
>> if test x0 = x1; then ../grub-macho2img xz_decompress.image xz_decompress.img; else objcopy -O binary --strip-unneeded -R .note -R .comment -R .note.gnu.build-id -R .reginfo -R .rel.dyn -R .note.gnu.gold-version xz_decompress.image xz_decompress.img; fi
>> BFD: Warning: Writing section `.text' to huge (ie negative) file offset 0x87cfff48.
>> BFD: Warning: Writing section `.rodata' to huge (ie negative) file offset 0x87d027b8.
>> BFD: Warning: Writing section `.data.rel.ro' to huge (ie negative) file offset 0x87d02834.
>> BFD: Warning: Writing section `.data' to huge (ie negative) file offset 0x87d02898.
>> BFD: Warning: Writing section `.got' to huge (ie negative) file offset 0x87d028a8.
>> objcopy:xz_decompress.img[.text]: File truncated
>> Makefile:41738: recipe for target 'xz_decompress.img' failed
>> make[5]: *** [xz_decompress.img] Error 1
>>
>> Any idea what's going on here? Let me know if I need to provide more
>> information.
>>
>
>
> Looks similar to
> http://www.linux-mips.org/archives/linux-mips/2006-06/msg00028.html.
To be more precise - Makefile is using
-Wl,-Ttext,$(TARGET_DECOMPRESSOR_LINK_ADDR) with
TARGET_DECOMPRESSOR_LINK_ADDR=0x88100000 for MIPS. It may need to
explicitly specify start address for other sections as well, somewhere
near 0x88100000.
next prev parent reply other threads:[~2014-08-26 8:23 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 [this message]
2014-09-21 15:52 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-09-23 15:49 ` Colin Watson
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='CAA91j0Xg2SmzjKctNXZ7B6objYqM49L8RVp0FLerL+ix1Nji=g@mail.gmail.com' \
--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).