public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Király Tamás" <kiraly.tamas@outlook.com>
To: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: some targets fail to build
Date: Wed, 12 Oct 2022 14:24:52 +0000	[thread overview]
Message-ID: <AS4PR01MB951896086C813C135E8513269C229@AS4PR01MB9518.eurprd01.prod.exchangelabs.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2068 bytes --]

Hi,

I downloaded binutils 2.39 and inspected bfd/config.bfd to generate a list of targets which should cover every cases. i then processed and reformatted the text to make it digestable to the ./configure --target <triplet>.

i found that using various triplets, building binutils fails. It mostly fails at configure part but some of them fail during compilation. There are various error messages like:

  *   ld does not support target
  *   This target is no longer supported in gas


here is a list of failing targets:

armb-unknown-freebsd
armb-unknown-linux
i386-unknown-knetbsd-gnu
sh1l-unknown-elf
sparcv-unknown-linux
ns32k-pc532-ux
aarch64_be-unknown-netbsd
arm-unknown-wince
aarch64-unknown-netbsd
arm-wrs-windiss
mipsel-unknown-openbsd
powerpc64-ibm-aix5.0
mips-unknown-openbsd
powerpc64-unknown-aix
powerpc64-ibm-aix5
mips-unknown-openbsd
mips-unknown-irix5
mips-unknown-irix6
shl-unknown-elf
powerpc-unknown-macos10
alpha-unknown-elf
alpha-unknown-none
i386-unknown-macos10
powerpc-unknown-rhapsody
x86_64-unknown-dicos
powerpc64-unknown-bsd
powerpc64le-unknown-bsd
mips-unknown-chorusrdb
powerpc-unknown-chorusrdb
mips-unknown-none
x86_64-unknown-pep
ns32k-unknown-lites
rs6000-unknown-none
pdp11-unknown-none
i386-unknown-rhapsody
powerpc-unknown-lynxos
powerpc-unknown-windiss
i386-unknown-dicos
bfin-unknown-none
m32r-unknown-none
m68k-unknown-none
metag-unknown-none
ns32k-unknown-bsd
nios2eb-unknown-none
nios2el-unknown-none
nios2-unknown-none
c30-unknown-coff
nds32le-unknown-none
nds32be-unknown-none
cr16-unknown-uclinux
vax-unknown-netbsdaout
vax-unknown-openbsd
amdgcn-unknown-none
i386-unknown-interix
m32rle-unknown-linux
m32rle-unknown-none
sh-unknown-openbsd
sparc64-unknown-none
sparc-unknown-none
z8k-unknown-none
sh-unknown-none


here is a repo with more details: https://gitlab.com/tkiraly/binutils

Maybe they are indeed bad triplets, i don't know, but probably bfd/config.bfd is less strict than it should. Anyone any thoughts?

regards
Tamás Király

             reply	other threads:[~2022-10-12 14:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 14:24 Király Tamás [this message]
2022-10-18 16:02 ` Nick Clifton

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=AS4PR01MB951896086C813C135E8513269C229@AS4PR01MB9518.eurprd01.prod.exchangelabs.com \
    --to=kiraly.tamas@outlook.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).