public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jeff Law <law@porcupine.slc.redhat.com>
To: ross.alexander@uk.neceur.com
Cc: binutils@sources.redhat.com
Subject: Re: hppa64-hp-hpux11.00: HP ELF64 brokeness (incorrect .dynamic  section)
Date: Tue, 02 Jul 2002 11:20:00 -0000	[thread overview]
Message-ID: <200207021823.g62INaY26693@porcupine.slc.redhat.com> (raw)
In-Reply-To: Your message of "Tue, 02 Jul 2002 16:56:59 BST." <OF57EE2279.B5306762-ON80256BEA.0056AFF9@uk.neceur.com>

In message <OF57EE2279.B5306762-ON80256BEA.0056AFF9@uk.neceur.com>, ross.alexan
der@uk.neceur.com writes:
  >
  > I don't mind producing a patch to create a workaround (it is very straight
  > forward, for a change) or we could produce a program which 'corrects' the
  > defective libraries.  However, because these are system libraries, a lot
  > of people may be unwilling to go near then.
I suspect "fixing" the defective libraries won't be palatable to most 
folks.  If we can engineer a clean workaround in bfd so that we can deal
with the broken libraries in a sane way that would probably be best.

jeff

  reply	other threads:[~2002-07-02 18:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-02  8:57 ross.alexander
2002-07-02 11:20 ` Jeff Law [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-04  4:18 ross.alexander
2002-07-04  6:39 ` Alan Modra
2002-07-03 12:45 John David Anglin
2002-07-03 13:10 ` Jeff Law
2002-07-03  5:14 ross.alexander
2002-07-04  0:19 ` Alan Modra
2002-07-01  8:16 ross.alexander
2002-07-01 16:18 ` Alan Modra
2002-06-28 12:07 ross.alexander
2002-06-30  4:12 ` Alan Modra

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=200207021823.g62INaY26693@porcupine.slc.redhat.com \
    --to=law@porcupine.slc.redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=law@redhat.com \
    --cc=ross.alexander@uk.neceur.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).