linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Metcalf <cmetcalf@mellanox.com>
To: Arnd Bergmann <arnd@arndb.de>, Peter Zijlstra <peterz@infradead.org>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	<linux-next@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-arch@vger.kernel.org>
Subject: Re: linux-next: Tree for Jun 21
Date: Wed, 22 Jun 2016 16:43:15 -0400	[thread overview]
Message-ID: <cea1e8b0-f0ca-7985-39f5-b66cfed50a9a@mellanox.com> (raw)
In-Reply-To: <3813680.TbHyagWbHe@wuerfel>

On 6/21/2016 5:14 PM, Arnd Bergmann wrote:
> On Tuesday, June 21, 2016 8:50:48 PM CEST Peter Zijlstra wrote:
>>> So what's your build process for the cross tools, by the way?  I'm assuming
>>> you're not doing a total bootstrap cross-tool build since you'd need minimal
>>> kernel headers (linux/errno.h or whatever) in that case.  I assume you're using
>>> the host headers to build the cross tool?
>>>
>>> So I'm a little confused how the other kernel headers are working out for you,
>>> e.g. <arch/icache.h> is referenced when building the tilegx libgcc.
>> I've no idea; I use this thing:
>>
>>    git://git.infradead.org/users/segher/buildall.git
>>
>> Although I've got some local modifications, none are to the actual
>> toolchain building part (although I suppose I should send segher a
>> patch).
>>
>> I have binutils-gdb.git and gcc.bit checkouts and point the buildall
>> config to that (both are on latest stable branches binutils-2_26-branch
>> and gcc-6-branch resp.). And I point the kernel path to my current
>> hacked up tree.
>>
>> I don't really rebuild the entire toolchains often, mostly only when I
>> really need a new GCC or its getting really old (like I used 5.3.0 for a
>> long while).
> I think the kernel headers are only needed for building glibc, which
> buildall.git doesn't use: it only does the initial stage of creating
> a cross-toolchain.

It turns out there were a few places where we were #include'ing Linux
headers in the gcc build (asm/unistd.h, arch/icache.h, arch/spr_def.h).
I patched gcc to provide inline copies of what was needed (pretty simple
stuff and won't ever change) and asked our lead compiler guy to upstream
it back up to gcc, so using buildall.git should get easier for tilepro/tilegx.

-- 
Chris Metcalf, Mellanox Technologies
http://www.mellanox.com

  reply	other threads:[~2016-06-22 20:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21  5:46 linux-next: Tree for Jun 21 Stephen Rothwell
2016-06-21  7:01 ` Sudip Mukherjee
2016-06-21  7:58   ` Peter Zijlstra
2016-06-21  8:55     ` Sudip Mukherjee
2016-06-21 12:08   ` Chris Metcalf
2016-06-21 12:42     ` Peter Zijlstra
2016-06-21 13:47       ` Chris Metcalf
2016-06-21 14:04         ` Peter Zijlstra
2016-06-21 14:14           ` Peter Zijlstra
2016-06-21 14:20             ` Chris Metcalf
2016-06-21 14:25               ` Peter Zijlstra
2016-06-21 14:34             ` Sudip Mukherjee
2016-06-21 15:26             ` Chris Metcalf
2016-06-21 17:06               ` Peter Zijlstra
2016-06-21 17:29                 ` Peter Zijlstra
2016-06-21 18:28                   ` Peter Zijlstra
2016-06-21 18:36                     ` Chris Metcalf
2016-06-21 18:50                       ` Peter Zijlstra
2016-06-21 19:04                         ` Peter Zijlstra
2016-06-21 21:14                         ` Arnd Bergmann
2016-06-22 20:43                           ` Chris Metcalf [this message]
2016-06-22 21:05                             ` Peter Zijlstra
2016-06-22  9:16                       ` Peter Zijlstra
2016-06-22 20:40                         ` Chris Metcalf
2016-06-24  8:58                         ` [tip:locking/arch-atomic] locking/atomic, arch/tile: Fix tilepro build tip-bot for Peter Zijlstra
  -- strict thread matches above, loose matches on Subject: below --
2023-06-21  4:59 linux-next: Tree for Jun 21 Stephen Rothwell
2022-06-21  9:35 Stephen Rothwell
2021-06-21 12:16 Stephen Rothwell
2020-06-21 15:23 Stephen Rothwell
2019-06-21 11:01 Stephen Rothwell
2018-06-21  4:11 Stephen Rothwell
2017-06-21  8:09 Stephen Rothwell
2015-06-21 10:50 Stephen Rothwell
2013-06-21  8:17 Stephen Rothwell
2012-06-21  6:12 Stephen Rothwell

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=cea1e8b0-f0ca-7985-39f5-b66cfed50a9a@mellanox.com \
    --to=cmetcalf@mellanox.com \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sudipm.mukherjee@gmail.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 NNTP newsgroup(s).