Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1428185
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: linux-next: Tree for Jun 21 |
| Date | 2016-06-21 23:30 +0200 |
| Message-ID | <rMBp8-2Kp-19@gated-at.bofh.it> (permalink) |
| References | <rMthU-5Vb-15@gated-at.bofh.it> <rMzdE-1pq-17@gated-at.bofh.it> <rMzdE-1pq-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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. Arnd
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
linux-next: Tree for Jun 21 Stephen Rothwell <sfr@canb.auug.org.au> - 2016-06-21 07:50 +0200
Re: linux-next: Tree for Jun 21 Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2016-06-21 09:10 +0200
Re: linux-next: Tree for Jun 21 Peter Zijlstra <peterz@infradead.org> - 2016-06-21 10:50 +0200
Re: linux-next: Tree for Jun 21 Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2016-06-21 11:00 +0200
Re: linux-next: Tree for Jun 21 Peter Zijlstra <peterz@infradead.org> - 2016-06-21 14:50 +0200
Re: linux-next: Tree for Jun 21 Peter Zijlstra <peterz@infradead.org> - 2016-06-21 16:20 +0200
Re: linux-next: Tree for Jun 21 Peter Zijlstra <peterz@infradead.org> - 2016-06-21 16:30 +0200
Re: linux-next: Tree for Jun 21 Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2016-06-21 16:40 +0200
Re: linux-next: Tree for Jun 21 Peter Zijlstra <peterz@infradead.org> - 2016-06-21 19:10 +0200
Re: linux-next: Tree for Jun 21 Peter Zijlstra <peterz@infradead.org> - 2016-06-21 19:40 +0200
Re: linux-next: Tree for Jun 21 Peter Zijlstra <peterz@infradead.org> - 2016-06-21 20:30 +0200
Re: linux-next: Tree for Jun 21 Peter Zijlstra <peterz@infradead.org> - 2016-06-21 21:10 +0200
Re: linux-next: Tree for Jun 21 Peter Zijlstra <peterz@infradead.org> - 2016-06-21 22:50 +0200
Re: linux-next: Tree for Jun 21 Arnd Bergmann <arnd@arndb.de> - 2016-06-21 23:30 +0200
Re: linux-next: Tree for Jun 21 Peter Zijlstra <peterz@infradead.org> - 2016-06-22 23:10 +0200
Re: linux-next: Tree for Jun 21 Peter Zijlstra <peterz@infradead.org> - 2016-06-22 11:20 +0200
Re: linux-next: Tree for Jun 21 Peter Zijlstra <peterz@infradead.org> - 2016-06-21 16:30 +0200
csiph-web