From: Ian Lance Taylor <ian@cygnus.com>
To: joel@OARcorp.com, eric@skatter.USask.Ca
Cc: gas2@cygnus.com
Subject: Re: binutils-2.9 objcopy fails (fwd)
Date: Tue, 14 Apr 1998 13:18:00 -0000 [thread overview]
Message-ID: <199804142018.QAA16481@subrogation.cygnus.com> (raw)
In-Reply-To: <Pine.BSF.3.96.980414142247.1247Q-100000@vespucci.advicom.net>
Date: Tue, 14 Apr 1998 14:23:14 -0500 (CDT)
From: Joel Sherrill <joel@OARcorp.com>
---------- Forwarded message ----------
Date: Tue, 14 Apr 98 13:20:47 -0600
From: Eric Norum <eric@skatter.USask.Ca>
I downloaded and installed the latest binutils. Now I can't
generate prom images any more.
Background:
I've got two types of 68360 systems here. One uses a single 8-bit
bootstrap prom and the other uses 4 8-bit bootstrap proms as a 32-bit
prom. I use a script to generate the S-record images for my prom
burner.
Here are the salient lines from the script:
m68k-rtems-objcopy --output-target=srec prom.exe prom.hex
for byte in 0 1 2 3
do
m68k-rtems-objcopy --interleave=4 --byte=$byte
--output-target=srec prom.exe prom$byte.hex
done
Problem:
The first objcopy works fine to build the 8-bit bootstrap prom
image, but when I try to split the executable into the 4 images for
the 32-bit prom, I get:
+ m68k-rtems-objcopy --output-target=srec prom.exe prom.hex
+ m68k-rtems-objcopy --interleave=4 --byte=0 --output-target=srec
prom.exe prom0.hex
m68k-rtems-objcopy: prom0.hex: Invalid operation
I can recreate this problem, but what's odd is that all of the code is
old. What version of the binutils were you using before? I can
recreate the problem using an binutils 2.6 I have lying around.
The problem I'm seeing is this call in copy_section in
binutils/objcopy.c:
/* The section has gotten smaller. */
if (!bfd_set_section_size (obfd, osection, size))
nonfatal (bfd_get_filename (obfd));
This is trying to set the section size after objcopy has already
started to write to the sections. This needs to be handled
differently.
Ian
next prev parent reply other threads:[~1998-04-14 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-14 12:49 Joel Sherrill
1998-04-14 13:18 ` Ian Lance Taylor [this message]
1998-04-14 13:18 Joel Sherrill
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=199804142018.QAA16481@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=eric@skatter.USask.Ca \
--cc=gas2@cygnus.com \
--cc=joel@OARcorp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).