From: sathesh babu <sathesh_edara2003@yahoo.co.in>
To: Jim Gifford <maillist@jg555.com>, Jim Wilson <wilson@specifix.com>
Cc: sathesh babu <sathesh_edara2003@yahoo.co.in>, linux-mips@linux-mips.org
Subject: Re: linux-libc-headers-2.6.17
Date: Thu, 21 Sep 2006 13:31:55 +0100 (BST) [thread overview]
Message-ID: <20060921123155.69745.qmail@web7913.mail.in.yahoo.com> (raw)
In-Reply-To: <4512134B.40006@jg555.com>
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
Hi Jim,
Thanks alot.
Does http://ftp.jg555.com/headers/ site already have sanitized headers?.
That means can i use http://ftp.jg555.com/headers/linux-headers-2.6.17.tar.bz2 sources as sanitized headers to build toolchain for Linux-2.6.17.
If Yes, can i directly use these sources in buildroot to build the toolchain?
Regards,
Sathesh
Jim Gifford <maillist@jg555.com> wrote:
Jim Wilson wrote:
> I'd suggest looking at Dan Kegel's crosstool package, which provides
> scripts showing how to do a build from scratch. There is a pointer to
> it on the www.linux-mips.org wiki. See
> http://www.linux-mips.org/wiki/Toolchains
>
Actually my Cross-LFS team has created a sanitation script to clean the
headers, you can get the script from http://headers.cross-lfs.org, or
you can download a bundle from http://ftp.jg555.com/headers
---------------------------------
Find out what India is talking about on - Yahoo! Answers India
Send FREE SMS to your friend's mobile from Yahoo! Messenger Version 8. Get it NOW
[-- Attachment #2: Type: text/html, Size: 1660 bytes --]
next prev parent reply other threads:[~2006-09-21 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 9:18 linux-libc-headers-2.6.17 sathesh babu
2006-09-20 19:07 ` linux-libc-headers-2.6.17 Jim Wilson
2006-09-21 4:21 ` linux-libc-headers-2.6.17 Jim Gifford
2006-09-21 12:31 ` sathesh babu [this message]
2006-10-03 14:35 ` linux-libc-headers-2.6.17 sathesh babu
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=20060921123155.69745.qmail@web7913.mail.in.yahoo.com \
--to=sathesh_edara2003@yahoo.co.in \
--cc=linux-mips@linux-mips.org \
--cc=maillist@jg555.com \
--cc=wilson@specifix.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