Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Jason R Thorpe <thorpej@wasabisystems.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFA] arm-netbsdelf cross-debugging fixes
Date: Mon, 02 Sep 2002 12:56:00 -0000	[thread overview]
Message-ID: <3D73C27C.3000704@ges.redhat.com> (raw)
In-Reply-To: <20020901165843.B4034@dr-evil.shagadelic.org>

> Unfortunately, the change disables "gdb_multi_arch=yes" for the
> arm-*-netbsd* entry in configure.tgt.  The reason for this is that
> the tm file needs to include "solib.h".  As far as I can tell, no
> platforms with shared libraries can be fully multi-arch until all
> the solib stuff is multi-arch'd.

Yes, known problem.  Downgrading is still the accepted workaround.
I'm not an Arm maintainer :-)

Andrew



  reply	other threads:[~2002-09-02 19:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-01 16:58 Jason R Thorpe
2002-09-02 12:56 ` Andrew Cagney [this message]
2002-09-03 12:23 ` Richard Earnshaw
2002-09-03 12:34   ` Jason R Thorpe
2002-09-04  4:10     ` Richard Earnshaw
2002-09-03 15:40   ` Jason R Thorpe
2002-09-04  2:56     ` Richard Earnshaw

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=3D73C27C.3000704@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=thorpej@wasabisystems.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