public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot]  Please pull ARC changes
Date: Thu, 15 Feb 2018 12:53:52 +0000	[thread overview]
Message-ID: <1518699232.5202.24.camel@synopsys.com> (raw)

Hi Tom,

This is just a quite subtle fix that allows to use Elf32 toolchain
for building U-Boot so I do believe it qualifies for the next RC and
some technical background below.

For quite some time we used to use uClibc toolchain for building U-Boot
just because it was our default toolchain. But when I tried to use
pre-built toolchain from kernel.org for example this one:
https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/7.3.0/x86_64-gcc-7.3.0-nolibc_arc-elf.tar.gz

I bumped into a trivial problem which is solved now.
That said recent kernel.org toolchains could be used for ARC once
buildman switches to them.

Anyways...

The following changes since commit 0c502b6c176281a096a23803e517b19e964485f1:

  configs: Resync with savedefconfig (2018-02-14 21:34:50 -0500)

are available in the Git repository at:

  git://git.denx.de/u-boot-arc.git 

for you to fetch changes up to d53b128df40d8b2f5dd87cac194163fca2bc17ed:

  arc: Fix final linkage with Elf32 tools (2018-02-15 15:44:47 +0300)

----------------------------------------------------------------
Alexey Brodkin (1):
      arc: Fix final linkage with Elf32 tools

 arch/arc/config.mk | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-Alexey

             reply	other threads:[~2018-02-15 12:53 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15 12:53 Alexey Brodkin [this message]
2018-02-15 19:07 ` [U-Boot] Please pull ARC changes Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2019-01-25  5:52 Alexey Brodkin
2019-01-27  3:50 ` Tom Rini
2018-12-03 11:32 Alexey Brodkin
2018-12-03 15:32 ` Tom Rini
2018-11-01 20:41 Alexey Brodkin
2018-11-02 20:30 ` Tom Rini
2018-10-15 10:22 Alexey Brodkin
2018-10-12 12:38 Alexey Brodkin
2018-10-05 14:10 Alexey Brodkin
2018-10-06  1:16 ` Tom Rini
2018-06-21 11:59 Alexey Brodkin
2018-06-21 18:21 ` Tom Rini
2018-06-18  9:29 Alexey Brodkin
2018-06-15 13:14 Alexey Brodkin
2018-06-16  2:34 ` Tom Rini
2018-05-24 13:09 Alexey Brodkin
2018-05-24 23:41 ` Tom Rini
2018-03-23 13:23 Alexey Brodkin
2018-03-23 13:33 ` Tom Rini
2018-03-23 13:38   ` Alexey Brodkin
2018-03-23 13:51     ` Tom Rini
2018-01-19 15:08 Alexey Brodkin
2018-01-19 21:11 ` Tom Rini
2017-12-12 15:52 Alexey Brodkin
2017-12-12 15:58 ` Tom Rini
2017-12-11  8:43 Alexey Brodkin
2017-12-12  1:55 ` Tom Rini
2017-11-24 16:39 Alexey Brodkin
2017-11-24 21:33 ` Tom Rini
2017-06-29 16:39 Alexey Brodkin
2017-06-30  1:26 ` Tom Rini
2017-04-11 14:56 Alexey Brodkin
2017-04-11 15:55 ` Tom Rini
2017-03-31 19:12 Alexey Brodkin
2017-04-04 20:00 ` Tom Rini
2017-03-24 11:53 Alexey Brodkin
2017-03-24 17:37 ` Tom Rini
2016-09-16 11:30 Alexey Brodkin
2016-09-19  0:31 ` Tom Rini
2016-08-05 10:09 Alexey Brodkin
2016-08-06  2:09 ` Tom Rini
2016-07-04  8:49 Alexey Brodkin
2016-07-05  2:44 ` Tom Rini
2016-06-13 12:43 Alexey Brodkin
2016-06-19 14:08 ` Tom Rini
2016-04-21 17:11 Alexey Brodkin
2016-04-22 14:26 ` Tom Rini
2016-04-11 17:23 Alexey Brodkin
2016-04-12  2:27 ` Tom Rini
2016-02-20  8:22 Alexey Brodkin
2016-02-20 14:23 ` Tom Rini
2015-12-08 14:33 Alexey Brodkin
2015-12-08 15:00 ` Tom Rini
2015-11-17 21:41 Alexey Brodkin
2015-11-18  0:50 ` Tom Rini

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=1518699232.5202.24.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=u-boot@lists.denx.de \
    /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