public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Gary Oblock <gary@amperecomputing.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: Need binutils target corresponding to GCC target arm-zephyr-eadi
Date: Wed, 22 Jun 2022 19:12:51 +0000	[thread overview]
Message-ID: <BYAPR01MB5464763F67D7E405A1C1167DC6B29@BYAPR01MB5464.prod.exchangelabs.com> (raw)
In-Reply-To: <ef8aad2b-b574-332a-38f7-95dfe78b393b@redhat.com>

Nick,

The eadi was a typo and of course it was eabi...

Thanks,

Gary
________________________________
From: Nick Clifton <nickc@redhat.com>
Sent: Wednesday, June 22, 2022 4:24 AM
To: Gary Oblock <gary@amperecomputing.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: Need binutils target corresponding to GCC target arm-zephyr-eadi

[EXTERNAL EMAIL NOTICE: This email originated from an external sender. Please be mindful of safe email handling and proprietary information protection practices.]


Hi Gary,

> Note, I'm not very familiar with building binutils and have zero
> experience with cross building it for use as in an embedded
> cross development environment. Any hints tips or pointers
> to tutorials will be a big help.

I am not familiar with the "eadi" environment, and as far as I know
the binutils does not support it.  If it is similar to the "eabi"
environment then you may be in luck, as that is supported by the
binutils.

There is a README file in the binutils/ subdirectory of the binutils
sources which explains the process for configuring and building the
binutils.

There may also be pre-built versions of cross targeted binutils
available for your use, without you having to compile anything,
although this does depend upon your development environment.

Cheers
   Nick


      reply	other threads:[~2022-06-22 19:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21 23:37 Gary Oblock
2022-06-22 11:24 ` Nick Clifton
2022-06-22 19:12   ` Gary Oblock [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=BYAPR01MB5464763F67D7E405A1C1167DC6B29@BYAPR01MB5464.prod.exchangelabs.com \
    --to=gary@amperecomputing.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.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).