From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: [25641] trunk/buildroot/target/linux
Date: Mon, 16 Mar 2009 11:47:56 +0100 [thread overview]
Message-ID: <1237200476.5838.461.camel@grond> (raw)
In-Reply-To: <20090313043143.8D1F07643C@busybox.osuosl.org>
fre 2009-03-13 klockan 04:31 +0000 skrev correa at uclibc.org:
> Author: correa
> Date: 2009-03-13 04:31:43 +0000 (Fri, 13 Mar 2009)
> New Revision: 25641
>
> Log:
> Fix build (dependency) with custom patch option
>
> Modified:
> trunk/buildroot/target/linux/Makefile.in.advanced
>
>
> Changeset:
> Modified: trunk/buildroot/target/linux/Makefile.in.advanced
> ===================================================================
> --- trunk/buildroot/target/linux/Makefile.in.advanced 2009-03-12 23:04:19 UTC (rev 25640)
> +++ trunk/buildroot/target/linux/Makefile.in.advanced 2009-03-13 04:31:43 UTC (rev 25641)
> @@ -71,7 +71,7 @@
> LINUX26_BSP_PATCH:=$(strip $(subst ",,$(BR2_LINUX_BSP_PATCH)))
> #"))
>
> -LINUX_HEADERS_DEPENDS:= $(LINUX26_BSP_PATCH)
> +LINUX_HEADERS_DEPENDS:= $(DL_DIR)/$(LINUX26_BSP_PATCH)
>
This patch breaks the build.
If $(LINUX26_BSP_PATCH) is empty, then you depend
on the download directory, which is touched
every time you download a new file, forcing the
rebuild of Linux.
If there is a patch applied, this gets applied once more
and the build fails.
Pls fix.
BR
Ulf Samuelsson
> ifneq ($(LINUX26_PATCH_SOURCE),)
> LINUX_HEADERS_DEPENDS+=$(DL_DIR)/$(LINUX26_PATCH_SOURCE)
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2009-03-16 10:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 4:31 [Buildroot] svn commit: [25641] trunk/buildroot/target/linux correa at uclibc.org
2009-03-16 10:47 ` Ulf Samuelsson [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=1237200476.5838.461.camel@grond \
--to=ulf.samuelsson@atmel.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