From: Joel Sherrill <joel@OARcorp.com>
To: Ian Lance Taylor <ian@cygnus.com>
Cc: gas2@cygnus.com
Subject: Re: more on powerpc-rtems ar failure
Date: Fri, 17 Apr 1998 09:01:00 -0000 [thread overview]
Message-ID: <Pine.BSF.3.96.980417105127.17786g-100000@vespucci.advicom.net> (raw)
In-Reply-To: <199804171544.LAA03190@subrogation.cygnus.com>
On Fri, 17 Apr 1998, Ian Lance Taylor wrote:
> Is this just that the code to check for "wrong format" was missing? So
> now it prints a better message?
>
> With the patch I sent, ar works correctly when configured with
> --enable-targets=all. It's still possible to have ambiguity problems
> with --enable-targets=all, but this one wasn't an ambiguity problem.
> It was a bug.
So powerpc-rtems should complete a build now with --enable-targets=all?
I am switching away from doing this based on your comments.
> Were you able to reproduce Eric Norum's Srecord split problem? Did you
> get all the information you wanted?
>
> Yes, I was able to reproduce it. The bug appears to have been there
> for a long time. I haven't looked into fixing it yet. The patch
> would be to calculate the correct section size in setup_sections
> rather than in copy_sections.
Great. We were not as concerned with when it was fixed as much as if the
report was reproducible and good enough to get fixed sometime. Eric found
a work-around.
--joel
next prev parent reply other threads:[~1998-04-17 9:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-16 13:26 Joel Sherrill
1998-04-16 14:03 ` Ian Lance Taylor
1998-04-16 15:36 ` Joel Sherrill
1998-04-16 14:43 ` Ian Lance Taylor
1998-04-16 14:55 ` Joel Sherrill
1998-04-16 14:55 ` Ian Lance Taylor
1998-04-16 15:02 ` Joel Sherrill
1998-04-16 15:36 ` Ian Lance Taylor
1998-04-17 5:55 ` Joel Sherrill
1998-04-17 8:44 ` Ian Lance Taylor
1998-04-17 9:01 ` Joel Sherrill [this message]
1998-04-17 9:01 ` Ian Lance Taylor
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=Pine.BSF.3.96.980417105127.17786g-100000@vespucci.advicom.net \
--to=joel@oarcorp.com \
--cc=gas2@cygnus.com \
--cc=ian@cygnus.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).