From: Daniel Laird <danieljlaird@hotmail.com>
To: linux-mips@linux-mips.org
Subject: Re: Install Headers Target
Date: Thu, 18 Jan 2007 04:53:01 -0800 (PST) [thread overview]
Message-ID: <8430190.post@talk.nabble.com> (raw)
In-Reply-To: <8426876.post@talk.nabble.com>
Daniel Laird wrote:
>
> I have been trying to build a kernel, toolchain and rootfs using
> buildroot.
>
> Buildroot uses the install-headers target of the kernel to get the headers
> to build a toolchain.
> I tried to build a the uClibc-gcc toolchain combo was missing 2 header
> files to do the build.
> This I fixed by patching Kbuild in asm-mips dir
> See below:
> diff -urN overlay_orig/include/asm-mips/Kbuild
> overlay/include/asm-mips/Kbuild
> --- a/include/asm-mips/Kbuild 2007-01-17 12:57:20.000000000 +0000
> +++b/include/asm-mips/Kbuild 2007-01-17 12:53:46.000000000 +0000
> @@ -1,3 +1,3 @@
> include include/asm-generic/Kbuild.asm
>
> -header-y += cachectl.h sgidefs.h sysmips.h
> +header-y += asm.h cachectl.h regdef.h sgidefs.h sysmips.h
>
> Is it possible for this to go in? (Any one any problems with this patch)
> Is this mailing list the correct one for this patch?
>
> Hope it helps
> Daniel Laird
>
>
Ok, Must be because I am using a released version of uClibc (hence 0.9.28)
and therefore not picked up the necessary fixes. This should go when 0.9.29
is released!!
Daniel
--
View this message in context: http://www.nabble.com/Install-Headers-Target-tf3032928.html#a8430190
Sent from the linux-mips main mailing list archive at Nabble.com.
prev parent reply other threads:[~2007-01-18 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 8:45 Install Headers Target Daniel Laird
2007-01-18 11:06 ` Thiemo Seufer
2007-01-18 11:22 ` Atsushi Nemoto
2007-01-18 12:53 ` Daniel Laird [this message]
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=8430190.post@talk.nabble.com \
--to=danieljlaird@hotmail.com \
--cc=linux-mips@linux-mips.org \
/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