From: William Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Apply kernel board patches when do linux26-menuconfig
Date: Fri, 02 Oct 2009 14:03:24 +0100 [thread overview]
Message-ID: <4AC5FA1C.1010100@carallon.com> (raw)
currently if you have not yet built/upacked linux and you run
linux26-menuconfig which unpacks linux and applies patches. However it
does not apply board (or arch) specific patches as would happen if you
built linux without opening the menuconfig.
Does that make sense? The patch below fixes it:
diff --git a/target/linux/Makefile.in.advanced
b/target/linux/Makefile.in.advanced
index b4774ca..4b2c451
--- a/target/linux/Makefile.in.advanced
+++ b/target/linux/Makefile.in.advanced
@@ -399,12 +399,12 @@ $(STAMP_DIR)/linux_modules_target_installed:
$(LINUX26_DIR)/.depend_done
fi
touch $@
-linux26-menuconfig: $(LINUX26_DIR)/.patched host-sed
+linux26-menuconfig: $(LINUX26_DIR)/.patched.board host-sed
[ -f $(LINUX26_DIR)/.config ] || cp $(LINUX26_KCONFIG)
$(LINUX26_DIR)/.config
$(MAKE) $(LINUX26_MAKE_FLAGS) -C $(LINUX26_DIR) menuconfig
-[ -f $(LINUX26_DIR)/.config ] && touch $(LINUX26_DIR)/.configured
-linux26-xconfig: $(LINUX26_DIR)/.patched host-sed
+linux26-xconfig: $(LINUX26_DIR)/.patched.board host-sed
[ -f $(LINUX26_DIR)/.config ] || cp $(LINUX26_KCONFIG)
$(LINUX26_DIR)/.config
$(MAKE) $(LINUX26_MAKE_FLAGS) -C $(LINUX26_DIR) xconfig
-[ -f $(LINUX26_DIR)/.config ] && touch $(LINUX26_DIR)/.configured
--
------------------------------------------------------------------------
Will Wagner will_wagner at carallon.com
Development Manager Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
reply other threads:[~2009-10-02 13:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4AC5FA1C.1010100@carallon.com \
--to=will_wagner@carallon.com \
--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