From: Nigel Stephens <nigel@mips.com>
To: zhuzhenhua <zzh.hust@gmail.com>
Cc: Thiemo Seufer <ths@networkno.de>, linux-mips <linux-mips@linux-mips.org>
Subject: Re: BFD: Warning: Writing section `.text' to huge (ie negative) file offset 0xa1ffff10
Date: Thu, 01 Jun 2006 13:49:56 +0100 [thread overview]
Message-ID: <447EE274.7060207@mips.com> (raw)
In-Reply-To: <50c9a2250606010356s63f6d6e7j255c77660d6f472a@mail.gmail.com>
zhuzhenhua wrote:
> On 6/1/06, Thiemo Seufer <ths@networkno.de> wrote:
>> zhuzhenhua wrote:
>> > i have write a code to link at 0xa2000000(uncached address)
>> > but when link i get the error as
>> > "BFD: Warning: Writing section `.text' to huge (ie negative) file
>> > offset 0xa1ffff10.
>> > BFD: Warning: Writing section `.data' to huge (ie negative) file
>> > offset 0xa200b050.
>> > BFD: Warning: Writing section `.reginfo' to huge (ie negative) file
>> > offset 0xa200c980.
>> > mipsel-linux-objcopy: /root/project/brec_flash/release/brec_flash.bin:
>> > File truncated
>> > make: *** [brec_flash] Error 1"
>> >
>> > my link.xn as follow:
>> >
>> > OUTPUT_ARCH(mips)
>> > ENTRY(brec_flash_entry)
>> > SECTIONS
>> > {
>> > .text 0xa2000000 :
>>
>> Use
>>
>> . = 0xa2000000;
>> .text :
>>
>> instead. "info ld" explains the subtle difference.
>>
>>
>> Thiemo
>>
>
> do you mean use
> . = 0xa2000000;
> .text :
> to replace
> .text 0xa2000000 :
> ?
> i modify as that, and it still get the same message
>
I think the problem is not with the linker, but in your use of objcopy
to convert your ELF file to a raw binary file.
1) What arguments are you giving to mipsel-linux-objcopy?
2) What is the output from mipsel-linux-objdump -h run on your
intermediate ELF object file?
Nigel
--
Nigel Stephens e. nigel@mips.com
MIPS Technologies p. +44 1223 203110
Building 7200 f. +44 1223 203181
Cambridge Research Park m. +44 7976 686470
Beach Road, Waterbeach w. http://www.mips.com
Cambridge CB5 9TL, UK
next prev parent reply other threads:[~2006-06-01 12:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 6:19 BFD: Warning: Writing section `.text' to huge (ie negative) file offset 0xa1ffff10 zhuzhenhua
2006-06-01 9:24 ` Thiemo Seufer
2006-06-01 10:56 ` zhuzhenhua
2006-06-01 12:49 ` Nigel Stephens [this message]
2006-06-02 0:49 ` zhuzhenhua
2006-06-02 2:50 ` zhuzhenhua
2006-06-02 9:48 ` Thiemo Seufer
2006-06-02 11:00 ` Nigel Stephens
2006-06-02 11:11 ` Nigel Stephens
2006-06-03 4:36 ` zhuzhenhua
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=447EE274.7060207@mips.com \
--to=nigel@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=ths@networkno.de \
--cc=zzh.hust@gmail.com \
/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