public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: "Király Tamás" <kiraly.tamas@outlook.com>,
	"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: some targets fail to build
Date: Tue, 18 Oct 2022 17:02:43 +0100	[thread overview]
Message-ID: <c388d404-038b-ca3b-c58b-d47cf787dd77@redhat.com> (raw)
In-Reply-To: <AS4PR01MB951896086C813C135E8513269C229@AS4PR01MB9518.eurprd01.prod.exchangelabs.com>

Hi Király,

> 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

It is possible that some of these target triples should be added to the
top level configure.ac file, in the code where it is constructing the
noconfigdirs variable.

> Maybe they are indeed bad triplets,

Bad is a strong word.  There are indeed ports where it is known that some
of the tools are not supported.  For example ports targeted at the darwin
execution environment do not support either an assembler or a linker.

> i don't know, but probably bfd/config.bfd is less strict than it should. Anyone any thoughts?

Yeah - it probably could be more strict, but I do not think that it is
really necessary.  The builder is told that the configuration is not
supported for the generation of a particular tool after all, even if it
is a little bit late in the configure/build process.

Cheers
   Nick


      reply	other threads:[~2022-10-18 16:02 UTC|newest]

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

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=c388d404-038b-ca3b-c58b-d47cf787dd77@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=kiraly.tamas@outlook.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).