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 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. > if it doesn't and there's a > problem with what that step produces in terms of headers, i'd submit a > patch to the kernel mailing list to take care of it. Yep. > currently, there are no patches applied to > linux-libc-headers-2.6.12.0, and there shouldn't be any needed for the > output from the latest kernel source tree. > does that sound reasonable? Yep. You should be safe and sound with that (provided you don't use git head). Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +0/33 662376056 | Software Designer | \ / CAMPAIGN | ^ | | --==< °_° >==-- °------------.-------: X AGAINST | /e\ There is no | | http://ymorin.is-a-geek.org/ | (*_*) | / \ HTML MAIL | """ conspiracy. | °------------------------------°-------°------------------°--------------------° -- 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] |