From: Joel Sherrill <joel@rtems.org>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: Obsolete beos
Date: Thu, 20 Oct 2022 14:04:01 -0500 [thread overview]
Message-ID: <CAF9ehCXYK_DscYqdfsPsMxMj50HgFLjJ6fH+1_BNDmpKic_uwQ@mail.gmail.com> (raw)
In-Reply-To: <Y1CMrFUC8d9lC/NL@squeak.grove.modra.org>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
What happens with Haiku? Does this impact it?
Not that I have any detailed knowledge about Haiku or Beos but I do know
they are related. :)
--joel
On Wed, Oct 19, 2022 at 6:48 PM Alan Modra via Binutils <
binutils@sourceware.org> wrote:
> See https://sourceware.org/pipermail/binutils/2021-September/117850.html
>
> * config.bfd: Obsolete *-*-beos*. Simplify x86 beos match.
>
> diff --git a/bfd/config.bfd b/bfd/config.bfd
> index 0ae8eb39d29..0bc27fdce97 100644
> --- a/bfd/config.bfd
> +++ b/bfd/config.bfd
> @@ -48,6 +48,7 @@ targ_underscore=no
>
> # Catch obsolete configurations.
> case $targ in
> + *-*-beos* | \
> null)
> if test "x$enable_obsolete" != xyes; then
> echo "*** Configuration $targ is obsolete." >&2
> @@ -751,7 +752,7 @@ case "${targ}" in
> targ_defvec=i386_pe_vec
> targ_selvecs="i386_pe_vec i386_pei_vec"
> ;;
> - i[3-7]86-*-beoself* | i[3-7]86-*-beos*)
> + i[3-7]86-*-beos*)
> targ_defvec=i386_elf32_vec
> targ_selvecs="iamcu_elf32_vec i386_pe_vec i386_pei_vec"
> ;;
>
> --
> Alan Modra
> Australia Development Lab, IBM
>
next prev parent reply other threads:[~2022-10-20 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 23:47 Alan Modra
2022-10-20 19:04 ` Joel Sherrill [this message]
2022-10-21 0:06 ` Alan Modra
2022-10-21 0:12 ` 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=CAF9ehCXYK_DscYqdfsPsMxMj50HgFLjJ6fH+1_BNDmpKic_uwQ@mail.gmail.com \
--to=joel@rtems.org \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
/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).