Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] Building 2.6.19 with Soekris 4801 target
Date: Tue, 5 Dec 2006 09:22:46 +0100	[thread overview]
Message-ID: <20061205082246.GA31644@aon.at> (raw)
In-Reply-To: <20061205075036.GB31372@aon.at>

On Tue, Dec 05, 2006 at 08:50:36AM +0100, Bernhard Fischer wrote:
>On Mon, Dec 04, 2006 at 09:37:41PM -0500, Eric Malkowski wrote:
>
>>So I made the following mod to toolchain/kernel-headers/kernel-headers.mk
>>to copy over the 2.6.19 top level Makefile to the linux headers dir and
>>voila:
>>
>>[malk at testbed buildroot]$ svn diff toolchain/kernel-headers/kernel-headers.mk
>>Index: toolchain/kernel-headers/kernel-headers.mk
>>===================================================================
>>--- toolchain/kernel-headers/kernel-headers.mk  (revision 16776)
>>+++ toolchain/kernel-headers/kernel-headers.mk  (working copy)
>>@@ -150,6 +150,7 @@
>> $(LINUX_HEADERS_DIR)/.configured: $(LINUX_HEADERS_UNPACK_DIR)/.patched
>>        (cd $(LINUX_HEADERS_UNPACK_DIR) ; \
>>         $(MAKE) ARCH=$(KERNEL_ARCH) INSTALL_HDR_PATH=$(LINUX_HEADERS_DIR)
>>headers_install)
>>+       cp $(LINUX_HEADERS_UNPACK_DIR)/Makefile $(LINUX_HEADERS_DIR)
>>        touch $(LINUX_HEADERS_DIR)/.configured
>> else
>> # the sanitized kernel-headers
>>
>
>Could you look if calling make prepare (or something like make

Ah, no. The old uClibc release had version checks that are removed for
good from uClibc trunk.

To please uClibc-0.9.28, we can copy the Makefile, but i ask you to
update the patch to delete that Makefile if the kernel version is >=
2.6.18 and uClibc-0.9.28 is used, right after the configure-step from
uClibc.

thanks,

  reply	other threads:[~2006-12-05  8:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-05  2:37 [Buildroot] Building 2.6.19 with Soekris 4801 target Eric Malkowski
2006-12-05  7:50 ` Bernhard Fischer
2006-12-05  8:22   ` Bernhard Fischer [this message]
2006-12-06  3:51     ` Eric Malkowski

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=20061205082246.GA31644@aon.at \
    --to=rep.nop@aon.at \
    --cc=buildroot@busybox.net \
    /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