From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: John Ericson <git@JohnEricson.me>
Cc: Alyssa Ross <hi@alyssa.is>, binutils@sourceware.org
Subject: GAS broken for m68k-netbsdelf (was: [PATCH v2] Make *-netbsd mean ELF rather than a.out for all CPU archs, deprecate ns32k-netbsd)
Date: Fri, 10 Sep 2021 16:52:05 +0200 [thread overview]
Message-ID: <20210910145205.tol7ebak4ewz6wvh@lug-owl.de> (raw)
In-Reply-To: <20210903201116.zdqagrrzodqsvrmc@lug-owl.de>
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
Hi John,
On Fri, 2021-09-03 22:11:16 +0200, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> On Tue, 2021-08-03 14:59:17 -0400, John Ericson <git@JohnEricson.me> wrote:
> > One possible concern was the status of NetBSD on NS32K, where only a.out
> > was supported. But per [1] NetBSD has removed support, and if it were to
> > come back, it would be with ELF. The binutils implementation is
> > therefore marked obsolete, per the instructions in the last message.
> >
> > With that patch and this one applied, I have confirmed the following:
> >
> > --target=i686-unknown-netbsd
> > --target=i686-unknown-netbsdelf
> > builds completely
> >
> > --target=i686-unknown-netbsdaout
> > properly fails because target is deprecated.
> >
> > --target=vax-unknown-netbsdaout builds completely except for gas, where
> > the target is deprecated.
>
> For my test builds, it seems that with --target=m68k-netbsdelf, a
> "make all-gas" fails:
>
> [all 2021-08-15 17:11:44] checking for sigsetjmp...
> [all 2021-08-15 17:11:44] checking linker --as-needed support... no
> [all 2021-08-15 17:11:44] checking for cos in -lm... yes
> [all 2021-08-15 17:11:44] *** Configuration m68k-unknown-netbsdelf is obsolete.
> [all 2021-08-15 17:11:44] *** Support has been REMOVED.
> [all 2021-08-15 17:11:44] make: *** [Makefile:3210: configure-opcodes] Error 1
>
> I guess that was not intended? (Still working at
> fd986183343387b019080d81838ad9371593b219, but broken at
> ec1e5afa895ea5f19f4b47d0e04fafe0a18f33ff.)
I wanted to give this a *ping*.
Thanks,
Jan-Benedict
--
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2021-09-10 14:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 23:01 Making *-netbsd-* to mean ELF not a.out for all CPUs John Ericson
2021-06-14 11:18 ` Nick Clifton
2021-06-18 1:59 ` John Ericson
2021-06-18 2:36 ` [PATCH] Remove `netbsdpe` support John Ericson
2021-06-29 15:48 ` Nick Clifton
2021-06-29 15:58 ` John Ericson
2021-07-18 22:32 ` [PATCH v2] " John Ericson
2021-07-21 1:38 ` Alan Modra
2021-07-06 19:55 ` [PATCH] Make *-netbsd mean ELF rather than a.out for all CPU archs John Ericson
2021-07-16 15:54 ` Nick Clifton
2021-07-18 22:00 ` John Ericson
2021-08-03 18:59 ` [PATCH v2] Make *-netbsd mean ELF rather than a.out for all CPU John Ericson
2021-08-03 18:59 ` [PATCH v2] Make *-netbsd mean ELF rather than a.out for all CPU archs, deprecate ns32k-netbsd John Ericson
2021-08-11 12:19 ` Nick Clifton
2021-09-03 20:11 ` Jan-Benedict Glaw
2021-09-10 14:52 ` Jan-Benedict Glaw [this message]
2021-09-13 7:34 ` GAS broken for m68k-netbsdelf (was: [PATCH v2] Make *-netbsd mean ELF rather than a.out for all CPU archs, deprecate ns32k-netbsd) Alan Modra
2021-07-20 17:14 ` Making *-netbsd-* to mean ELF not a.out for all CPUs Maciej W. Rozycki
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=20210910145205.tol7ebak4ewz6wvh@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=binutils@sourceware.org \
--cc=git@JohnEricson.me \
--cc=hi@alyssa.is \
/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).