From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] use same kernel in buildroot and in crosstool-ng
Date: Thu, 22 Sep 2011 11:55:51 +0200 [thread overview]
Message-ID: <20110922115551.57b5c6fb@skate> (raw)
In-Reply-To: <1316684171-24580-1-git-send-email-sinseman44@gmail.com>
Le Thu, 22 Sep 2011 11:36:11 +0200,
sinseman44 <sinseman44@gmail.com> a ?crit :
> + config KERNEL_LINUX_CUSTOM_TARBALL
Presumably the name of this option needs to be changed.
KERNEL_LINUX_CUSTOM_LOCATION or something like that.
> -HOST_CROSSTOOL_NG_DEPENDENCIES = host-gawk host-automake $(if $(BR2_CCACHE),host-ccache)
> +HOST_CROSSTOOL_NG_DEPENDENCIES = $(if $(BR2_TOOLCHAIN_CTNG_BUILDROOT_KERNEL), \
> + $(LINUX_TARGET_SOURCE) $(LINUX_TARGET_EXTRACT) $(LINUX_TARGET_PATCH) $(LINUX_TARGET_CONFIGURE)) \
> + host-gawk \
> + host-automake \
> + $(if $(BR2_CCACHE),host-ccache)
Something like:
HOST_CROSSTOOL_NG_DEPENDENCIES = host-gawk host-automake $(if $(BR2_CCACHE),host-ccache)
ifeq ($(BR2_TOOLCHAIN_CTNG_BUILDROOT_KERNEL),y)
HOST_CROSSTOOL_NG_DEPENDENCIES += linux-configure
endif
Would be a lot better.
> +config BR2_TOOLCHAIN_CTNG_BUILDROOT_KERNEL
> + bool "Buildroot kernel version"
Missing:
depends on BR2_LINUX_KERNEL
> + help
> + Use buildroot kernel version in crosstool-Ng
> +
> +CTNG_FIX_DOT_CONFIG_SED += s:^(CT_KERNEL_LINUX_CUSTOM_TARBALL)=.*:\1="$(BUILD_DIR)/linux-$(call qstrip,$(BR2_LINUX_KERNEL_VERSION))":;
$(LINUX_DIR) ?
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2011-09-22 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 9:36 [Buildroot] [PATCH] use same kernel in buildroot and in crosstool-ng sinseman44
2011-09-22 9:38 ` Vincent BENOIT
2011-09-22 9:55 ` Thomas Petazzoni [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=20110922115551.57b5c6fb@skate \
--to=thomas.petazzoni@free-electrons.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