public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Vineet Gupta <vgupta@synopsys.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	Guenter Roeck <linux@roeck-us.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-snps-arc@lists.infradead.org,
	Michael Ellerman <michael@ellerman.id.au>,
	Tony Breeds <tony@bakeyournoodle.com>
Subject: cross compilers [was build failure of sorts]
Date: Sat, 18 Jun 2016 12:17:40 +0200	[thread overview]
Message-ID: <20160618101740.GN30927@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160618070501.GC30154@twins.programming.kicks-ass.net>

On Sat, Jun 18, 2016 at 09:05:01AM +0200, Peter Zijlstra wrote:

> I use segher's buildall script.

> The buildall script I put to work and after about an hour I have however
> many of the 20+ targets that build with gcc.git and binutils.git cross
> compilers.
> 

Like the below...

(the native ones worked after I upgraded a lib and installed 32bit libs
because it wanted to build a multilib version)

As you can see, arc doesn't even build upstream binutils :/
(binutils-2_26-branch as of today).

/usr/local/src/buildall# time ./buildall --toolchain      
================== Primary platforms =========================
Building arm... (target arm-linux-gnueabi)
  binutils: configure [00:03] build [01:25] install [00:08]
       gcc: configure [00:04] build [01:14] install [00:12]
  OK
Building i386... (target i386-linux)
  binutils: configure [00:03] build [01:23] install [00:08]
       gcc: configure [00:03] build [01:22]  FAILED
Building mips... (target mips-linux)
  binutils: configure [00:05] build [01:26] install [00:08]
       gcc: configure [00:04] build [01:26] install [00:11]
  OK
Building mips64... (target mips64-linux)
  binutils: configure [00:03] build [01:29] install [00:07]
       gcc: configure [00:04] build [01:28] install [00:15]
  OK
Building powerpc... (target powerpc-linux)
  binutils: configure [00:03] build [01:36] install [00:07]
       gcc: configure [00:04] build [01:27] install [00:09]
  OK
Building powerpc64... (target powerpc64-linux)
  binutils: configure [00:03] build [01:37] install [00:08]
       gcc: configure [00:04] build [01:26] install [00:09]
  OK
Building sparc... (target sparc-linux)
  binutils: configure [00:03] build [01:21] install [00:08]
       gcc: configure [00:03] build [01:13] install [00:09]
  OK
Building sparc64... (target sparc64-linux)
  binutils: configure [00:03] build [01:23] install [00:08]
       gcc: configure [00:04] build [01:13] install [00:08]
  OK
Building x86_64... (target x86_64-linux)
  binutils: configure [00:03] build [02:16] install [00:09]
       gcc: configure [00:04]  FAILED
================== Secondary platforms =======================
Building arm64... (target aarch64-linux)
  binutils: configure [00:03] build [01:23] install [00:08]
       gcc: configure [00:04] build [01:12] install [00:20]
  OK
Building s390... (target s390-linux)
  binutils: configure [00:03] build [01:24] install [00:07]
       gcc: configure [00:04] build [02:03] install [00:09]
  OK
================== Tertiary platforms ========================
Building alpha... (target alpha-linux)
  binutils: configure [00:03] build [01:23] install [00:08]
       gcc: configure [00:04] build [01:10] install [00:08]
  OK
Building arc... (target arc-elf)
  binutils: configure [00:04] build [00:57]  FAILED
Building blackfin... (target bfin-uclinux)
  binutils: configure [00:02] build [01:27] install [00:08]
       gcc: configure [00:04] build [01:37] install [00:08]
  OK
Building c6x... (target c6x-elf)
  binutils: configure [00:03] build [01:24] install [00:07]
       gcc: configure [00:04] build [01:39]  FAILED
Building cris... (target cris-linux)
  binutils: configure [00:03] build [01:28] install [00:07]
       gcc: configure [00:04] build [01:11] install [00:09]
  OK
Building frv... (target frv-linux)
  binutils: configure [00:03] build [01:32] install [00:08]
       gcc: configure [00:04] build [01:10] install [00:10]
  OK
Building h8300... (target h8300-linux)
  binutils: configure [00:03] build [01:26] install [00:07]
       gcc: configure [00:04] build [01:17] install [00:09]
  OK
Building ia64... (target ia64-linux)
  binutils: configure [00:03] build [01:23] install [00:07]
       gcc: configure [00:04] build [01:10] install [00:08]
  OK
Building m32r... (target m32r-linux)
  binutils: configure [00:03] build [01:18]  FAILED
Building m68k... (target m68k-linux)
  binutils: configure [00:03] build [01:24] install [00:07]
       gcc: configure [00:04] build [01:17] install [00:09]
  OK
Building mn10300... (target am33_2.0-linux)
  binutils: configure [00:03] build [01:22] install [00:08]
       gcc: configure [00:04] build [01:08] install [00:08]
  OK
Building nios2... (target nios2-linux)
  binutils: configure [00:05] build [01:23] install [00:07]
       gcc: configure [00:05] build [01:10] install [00:08]
  OK
Building parisc... (target hppa-linux)
  binutils: configure [00:04] build [01:26] install [00:07]
       gcc: configure [00:04] build [01:12] install [00:08]
  OK
Building parisc64... (target hppa64-linux)
  binutils: configure [00:03] build [01:24] install [00:07]
       gcc: configure [00:05] build [01:11] install [00:08]
  OK
Building sh... (target sh4-linux)
  binutils: configure [00:04] build [01:27] install [00:07]
       gcc: configure [00:05] build [01:09] install [00:09]
  OK
Building shnommu... (target sh2-linux)
  binutils: configure [00:03] build [01:27] install [00:08]
       gcc: configure [00:04] build [01:15] install [00:08]
  OK
Building sh64... (target sh64-linux)
  binutils: configure [00:03] build [01:17]  FAILED
Building tile... (target tilegx-linux)
  binutils: configure [00:03] build [01:24] install [00:07]
       gcc: configure [00:04] build [01:32] install [00:09]
  OK
Building xtensa... (target xtensa-linux)
  binutils: configure [00:03] build [01:27] install [00:07]
       gcc: configure [00:05] build [01:09] install [00:08]
  OK
================== Imaginary platforms =======================
Building microblaze... (target microblaze-linux)
  binutils: configure [00:03] build [01:25] install [00:07]
       gcc: configure [00:05] build [01:27] install [00:09]
  OK

real    91m18.406s
user    376m21.856s
sys     50m34.916s

  reply	other threads:[~2016-06-18 10:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17 14:36 Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()' Guenter Roeck
2016-06-17 14:39 ` Peter Zijlstra
2016-06-17 14:41   ` Peter Zijlstra
2016-06-17 14:52     ` Guenter Roeck
2016-06-17 15:00       ` Vineet Gupta
2016-06-17 15:22         ` Peter Zijlstra
2016-06-17 15:36           ` Vineet Gupta
2016-06-17 16:04     ` Ingo Molnar
2016-06-17 16:13       ` Peter Zijlstra
2016-06-17 20:22       ` Vineet Gupta
2016-06-17 21:27         ` Guenter Roeck
2016-06-18  7:05         ` Peter Zijlstra
2016-06-18 10:17           ` Peter Zijlstra [this message]
2016-06-21  5:29             ` cross compilers [was build failure of sorts] Vineet Gupta
2016-06-21  7:43               ` Peter Zijlstra
2016-06-21  9:28                 ` Vineet Gupta
2016-06-21  9:45                   ` Peter Zijlstra
2016-06-21  9:59                     ` Vineet Gupta
2016-06-21 10:04                     ` Peter Zijlstra
2016-06-22 10:04     ` Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()' Vineet Gupta
2016-06-22 10:24       ` Peter Zijlstra

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=20160618101740.GN30927@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=linux@roeck-us.net \
    --cc=michael@ellerman.id.au \
    --cc=mingo@kernel.org \
    --cc=tony@bakeyournoodle.com \
    --cc=vgupta@synopsys.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