public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "John Ericson" <mail@johnericson.me>
To: binutils@sourceware.org, gcc@gcc.gnu.org
Cc: "Alyssa Ross" <hi@alyssa.is>
Subject: Making *-netbsd-* to mean ELF not a.out for all CPUs
Date: Fri, 11 Jun 2021 19:01:06 -0400	[thread overview]
Message-ID: <465efd4f-542c-48b9-8f2d-081b37c872fa@www.fastmail.com> (raw)

Hello Binutils and GCC lists[1],

I would like to propose that GNU tools consistently interpret configs with "netbsd" as meaning ELF as opposed to a.out. Currently, newer CPUs do that, but older ones have "netbsd" mean a.out for historical reasons, and "netbsdelf" is used instead. This inconsistency is a bit of a nuisance to my distro / package set[2] which aims to support cross compilation to/from arbitrary platforms without special cases. Other platforms that formerly used a.out (like Linux) have long since changed the default to be ELF, so I don't know why NetBSD shouldn't too.

I first reached out to the NetBSD toolchain developers[3]. They convinced me some alternate disambiguater (my first suggestion) wasn't worth it, with a.out being so old. But they did offer some tentative support for my second suggestion of changing the meaning of bare "netbsd" --- "netbsdaout" would still be available to unambiguously request a.out for anyone that wants it. I come now to just ask about that second suggestion.

I have prepared a first draft of patches for Binutils and GCC, but before polishing them off to submit, I figured I should ask about the openness to such a change.

Thanks,

John

[1]: I hope it's OK to email both lists at once like this; this is a question about a change that I think only makes sense if both projects approve.

[2] Nixpkgs, https://github.com/nixos/nixpkgs/

[3]: https://mail-index.netbsd.org/tech-toolchain/2021/06/10/msg003976.html this post goes more into more why I am interested in this change for anyone that's curious. Apologies for the duplicate emails; I thought the list was rejecting emails with HTML but it was something else.

             reply	other threads:[~2021-06-11 23:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11 23:01 John Ericson [this message]
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                 ` GAS broken for m68k-netbsdelf (was: [PATCH v2] Make *-netbsd mean ELF rather than a.out for all CPU archs, deprecate ns32k-netbsd) Jan-Benedict Glaw
2021-09-13  7:34                   ` 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=465efd4f-542c-48b9-8f2d-081b37c872fa@www.fastmail.com \
    --to=mail@johnericson.me \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --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).