From: Andrew Cagney <ac131313@redhat.com>
To: gdb@sources.redhat.com
Subject: Always multi-arch the SPARC, dump sparclet?
Date: Mon, 25 Nov 2002 13:17:00 -0000 [thread overview]
Message-ID: <3DE2937F.4010007@redhat.com> (raw)
Hello,
The SPARC target has a number of variants that don't yet build with
multi-arch enabled (e.g., sparc-elf).
I'd like to propose that the switch simply be thrown and any
non-multi-arch code be ripped out. Acceptance criteria for such a
change being simply `it still builds'.
This shouldn't affect things like GNU/Linux, which, I believe, do
already build with multi-arch enabled.
This will, however, affect non-nulti-arch SPARC targets such as the
sparclet potentially leading to breakage.
Thoughts?
Andrew
next reply other threads:[~2002-11-25 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 13:17 Andrew Cagney [this message]
2002-11-25 13:21 ` Daniel Jacobowitz
2002-11-25 13:28 ` Andrew Cagney
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=3DE2937F.4010007@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.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