This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Sun, 6 May 2007, Yann E. MORIN wrote: > On Saturday 05 May 2007 23:03, Robert P. J. Day wrote: > > the first step in building the toolchain is typically getting (and > > patching) the sanitized kernel headers. for this, i would simply use > > the latest kernel source tree via "git pull", and run: > > Not git pull: headers might not be stable in head. You'd better get the > lattest stable tarball (today: 2.6.21.1). > > > $ make ARCH=??? headers_install > > > > in a perfect world, what comes out of that should just plain work for > > the rest of the toolchain build, correct? > > Yep. I also assume this is correct in ct-NG. actually, i would probably start *precisely* with the headers based on "git pull" just so, if there was a recently introduced problem, i'd spot it immediately and could fix it ASAP. but other than that, we clearly agree here -- the pure, unaltered output from "make headers_install" should *theoretically* work as the kernel headers for crosstool. good. now, what about the next step involving binutils ...? :-) rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://fsdev.net/wiki/index.php?title=Main_Page ======================================================================== -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |