[Buildroot] Custom kernal patch not being run

[Buildroot] Custom kernal patch not being run

[buildrootcharles]

I am trying to figure out how to create and have buildroot deploy a custom
kernel patch (on my system only). I currently have my buildroot configured
to  build a custom kernel from a tarball I have saved locally on my machine
(filename Linux-3.10.4-July302014.tar.gz), I have created a patch file
(named Linux-patch.patch) with the following content:

*** /home/MSC/SVN_BuildRoot/output/build/linux-custom/net/ipv4/ipconfig.c
2014-07-22 14:45:55.000000000 -0700
--- /home/MSC/SVN_BuildRoot/board/ep4502/linux-patches/ipconfig.c	2014-08-28
10:00:33.824586558 -0700
***************
*** 89,96 ****
  
  /* Define the friendly delay before and after opening net devices */
  #define CONF_POST_OPEN		10	/* After opening: 10 msecs */
! #ifdef CONFIG_MACH_AT91SAM9G45_EP4502VBB
! #define CONF_CARRIER_TIMEOUT	12000	/* Wait for carrier timeout */
  #else
  #define CONF_CARRIER_TIMEOUT	120000	/* Wait for carrier timeout */
  #endif
--- 89,96 ----
  
  /* Define the friendly delay before and after opening net devices */
  #define CONF_POST_OPEN		10	/* After opening: 10 msecs */
! #ifdef CONFIG_MACH_AT91SAM9G45_EP4502MSC
! #define CONF_CARRIER_TIMEOUT	30000	/* Wait for carrier timeout */
  #else
  #define CONF_CARRIER_TIMEOUT	120000	/* Wait for carrier timeout */
  #endif

I have specified the directory where the patch resides in the
BR2_LINUX_KERNEL_PATCH="/home/patchdirectory/"
whenever I run make Linux-rebuild it never seems to find my patch, do I have
it named wrong?  can anyone help, I've been stuck on this for nearly 2 days?
thanks.



--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Custom-kernal-patch-not-being-run-tp78152.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

[Buildroot] Custom kernal patch not being run

[Thomas De Schampheleire]

Hi Charles,

buildrootcharles <charles.s@mercury-security.com> schreef:
>I am trying to figure out how to create and have buildroot deploy a custom
>kernel patch (on my system only). I currently have my buildroot configured
>to  build a custom kernel from a tarball I have saved locally on my machine
>(filename Linux-3.10.4-July302014.tar.gz), I have created a patch file
>(named Linux-patch.patch) with the following content:
>
>*** /home/MSC/SVN_BuildRoot/output/build/linux-custom/net/ipv4/ipconfig.c
>2014-07-22 14:45:55.000000000 -0700
>--- /home/MSC/SVN_BuildRoot/board/ep4502/linux-patches/ipconfig.c	2014-08-28
>10:00:33.824586558 -0700
>***************
>*** 89,96 ****
>  
>  /* Define the friendly delay before and after opening net devices */
>  #define CONF_POST_OPEN		10	/* After opening: 10 msecs */
>! #ifdef CONFIG_MACH_AT91SAM9G45_EP4502VBB
>! #define CONF_CARRIER_TIMEOUT	12000	/* Wait for carrier timeout */
>  #else
>  #define CONF_CARRIER_TIMEOUT	120000	/* Wait for carrier timeout */
>  #endif
>--- 89,96 ----
>  
>  /* Define the friendly delay before and after opening net devices */
>  #define CONF_POST_OPEN		10	/* After opening: 10 msecs */
>! #ifdef CONFIG_MACH_AT91SAM9G45_EP4502MSC
>! #define CONF_CARRIER_TIMEOUT	30000	/* Wait for carrier timeout */
>  #else
>  #define CONF_CARRIER_TIMEOUT	120000	/* Wait for carrier timeout */
>  #endif
>
>I have specified the directory where the patch resides in the
>BR2_LINUX_KERNEL_PATCH="/home/patchdirectory/"
>whenever I run make Linux-rebuild it never seems to find my patch, do I have
>it named wrong?  can anyone help, I've been stuck on this for nearly 2 days?
>thanks.
>

linux-rebuild will not reapply patches.
Try 
make linux-dirclean linux

Best regards,
Thomas

[Buildroot] Custom kernal patch not being run

[buildrootcharles]

Thanks Thomas, I just tried that command and it still does not implement my patch. When I execute the command "make linux-dirclean linux" I see text that says ">>> linux custom Download additional patches" is this supposed to indicate it found my patch? I'm guessing that I have the patch file named wrong as I have read it needs to match exactly what is trying to be patched but I don't know if it should be named linux-custom (that's the folder name in output->build->) should it be named the same as the custom kernel tarball (linux-3.10.4-July302014)?

From: Thomas De Schampheleire [via Buildroot (busybox)] [mailto:ml-node+s2317881n78153h8 at n4.nabble.com]
Sent: Thursday, August 28, 2014 11:36 AM
To: Charles Stahl
Subject: Re: Custom kernal patch not being run

Hi Charles,

buildrootcharles <[hidden email]</user/SendEmail.jtp?type=node&node=78153&i=0>> schreef:

>I am trying to figure out how to create and have buildroot deploy a custom
>kernel patch (on my system only). I currently have my buildroot configured
>to  build a custom kernel from a tarball I have saved locally on my machine
>(filename Linux-3.10.4-July302014.tar.gz), I have created a patch file
>(named Linux-patch.patch) with the following content:
>
>*** /home/MSC/SVN_BuildRoot/output/build/linux-custom/net/ipv4/ipconfig.c
>2014-07-22 14:45:55.000000000 -0700
>--- /home/MSC/SVN_BuildRoot/board/ep4502/linux-patches/ipconfig.c 2014-08-28
>10:00:33.824586558 -0700
>***************
>*** 89,96 ****
>
>  /* Define the friendly delay before and after opening net devices */
>  #define CONF_POST_OPEN 10 /* After opening: 10 msecs */
>! #ifdef CONFIG_MACH_AT91SAM9G45_EP4502VBB
>! #define CONF_CARRIER_TIMEOUT 12000 /* Wait for carrier timeout */
>  #else
>  #define CONF_CARRIER_TIMEOUT 120000 /* Wait for carrier timeout */
>  #endif
>--- 89,96 ----
>
>  /* Define the friendly delay before and after opening net devices */
>  #define CONF_POST_OPEN 10 /* After opening: 10 msecs */
>! #ifdef CONFIG_MACH_AT91SAM9G45_EP4502MSC
>! #define CONF_CARRIER_TIMEOUT 30000 /* Wait for carrier timeout */
>  #else
>  #define CONF_CARRIER_TIMEOUT 120000 /* Wait for carrier timeout */
>  #endif
>
>I have specified the directory where the patch resides in the
>BR2_LINUX_KERNEL_PATCH="/home/patchdirectory/"
>whenever I run make Linux-rebuild it never seems to find my patch, do I have
>it named wrong?  can anyone help, I've been stuck on this for nearly 2 days?
>thanks.
>

linux-rebuild will not reapply patches.
Try
make linux-dirclean linux

Best regards,
Thomas

_______________________________________________
buildroot mailing list
[hidden email]</user/SendEmail.jtp?type=node&node=78153&i=1>
http://lists.busybox.net/mailman/listinfo/buildroot

________________________________
If you reply to this email, your message will be added to the discussion below:
http://buildroot-busybox.2317881.n4.nabble.com/Custom-kernal-patch-not-being-run-tp78152p78153.html
To unsubscribe from Custom kernal patch not being run, click here<http://buildroot-busybox.2317881.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=78152&code=Y2hhcmxlcy5zQG1lcmN1cnktc2VjdXJpdHkuY29tfDc4MTUyfC0yMTA5MTYzODgw>.
NAML<http://buildroot-busybox.2317881.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>



This transmission may contain sensitive, confidential and/or privileged
information. The sender does not waive any privilege or confidentiality in the
event of an inadvertent transmission to an unauthorized recipient. In the event
of such a transmission, please kindly contact the sender and delete all copies of
email. It is the recipient's responsibility to check this email and any
attachments for viruses. Mercury Security and the sender accept no responsibility
whatsoever for any loss suffered as a result of a virus entering the recipient's
computer system. Thank you.



--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Custom-kernal-patch-not-being-run-tp78152p78154.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140828/64b712d2/attachment.html>

[Buildroot] Custom kernal patch not being run

[Thomas De Schampheleire]

Hi Charles,

(please don't top-post, and send mails in plaintext only)

On Thu, Aug 28, 2014 at 8:44 PM, buildrootcharles
<charles.s@mercury-security.com> wrote:
> Thanks Thomas, I just tried that command and it still does not implement my
> patch. When I execute the command ?make linux-dirclean linux? I see text
> that says ?>>> linux custom Download additional patches? is this supposed to
> indicate it found my patch? I?m guessing that I have the patch file named
> wrong as I have read it needs to match exactly what is trying to be patched
> but I don?t know if it should be named linux-custom (that?s the folder name
> in output->build->) should it be named the same as the custom kernel tarball
> (linux-3.10.4-July302014)?
>

The option BR2_LINUX_KERNEL_PATCH can contain just the directory name,
and this directory does not have any naming requirement.

The patches themselves should be named linux-something.patch. In your
original mail you wrote Linux-something.patch, with a capital L which
is not correct.

What you're supposed to see is something like:
>>> linux 3.16.1 Patching
for p in /tmp/foo/ ; do if echo $p | grep -q -E "^ftp://|^http://" ;
then support/scripts/apply-patches.sh
/home/tdescham/repo/contrib/buildroot-review/output/build/linux-3.16.1
/home/tdescham/repo/contrib/dl `basename $p` ; elif test -d $p ; then
support/scripts/apply-patches.sh
/home/tdescham/repo/contrib/buildroot-review/output/build/linux-3.16.1
$p linux-\*.patch ; else support/scripts/apply-patches.sh
/home/tdescham/repo/contrib/buildroot-review/output/build/linux-3.16.1
`dirname $p` `basename $p` ; fi done

Applying linux-bar.patch using patch:


In this example, I had:
BR2_LINUX_KERNEL_PATCH="/tmp/foo/"

and
$ find /tmp/foo
/tmp/foo
/tmp/foo/Linux-baz.patch
/tmp/foo/linux-bar.patch

Best regards,
Thomas

[Buildroot] Custom kernal patch not being run

[buildrootcharles]

Thomas, thanks again for the reply. I have tried what you suggested will no
luck. The only message I see regarding "patch" for my "make linux-dirclean
linux" command is ">>> linux custom Download additional patches". Could this
be an issue with the configuration I have related to my custom linux
tarball? The options I have selected in the Kernel options are:

[*] Linux Kernel
    Kernel version (Custom tarball)  --->
(file:///home/MSC/linux-3.10.4-July302014.tar.gz) URL of custom ...
(/home/MSC/BuildRoot/board/xxxx/linux-custom) Custom kernel patches
    Kernel configuration (Using a custom config file)  --->
(/home/MSC/customfile.config) Configuration file path
 
No other options selected



--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Custom-kernal-patch-not-being-run-tp78152p78157.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

[Buildroot] Custom kernal patch not being run

[Thomas De Schampheleire]

Hi Charles,

On Thu, Aug 28, 2014 at 10:43 PM, buildrootcharles
<charles.s@mercury-security.com> wrote:
> Thomas, thanks again for the reply. I have tried what you suggested will no
> luck. The only message I see regarding "patch" for my "make linux-dirclean
> linux" command is ">>> linux custom Download additional patches". Could this
> be an issue with the configuration I have related to my custom linux
> tarball? The options I have selected in the Kernel options are:
>
> [*] Linux Kernel
>     Kernel version (Custom tarball)  --->
> (file:///home/MSC/linux-3.10.4-July302014.tar.gz) URL of custom ...
> (/home/MSC/BuildRoot/board/xxxx/linux-custom) Custom kernel patches
>     Kernel configuration (Using a custom config file)  --->
> (/home/MSC/customfile.config) Configuration file path
>
> No other options selected
>

Which version of Buildroot are you using? Is this a recent release?

Also, please send us your .config so we can try to reproduce.

The message 'Downloading additional patches' should not appear for
local patches, i.e. those that are in a directory, but only for http
or ftp patches.

Best regards,
Thomas

[Buildroot] Custom kernal patch not being run

[buildrootcharles]

default.config
<http://buildroot-busybox.2317881.n4.nabble.com/file/n78215/default.config>  

> Which version of Buildroot are you using? Is this a recent release? 

I'm using Buildroot version 2013.08

> Also, please send us your .config so we can try to reproduce. 

config file attached (I renamed it default.config just for the upload)

> The message 'Downloading additional patches' should not appear for 
> local patches, i.e. those that are in a directory, but only for http 
> or ftp patches. 

> Best regards, 
> Thomas 



--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Custom-kernal-patch-not-being-run-tp78152p78215.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

[Buildroot] Custom kernal patch not being run

[Thomas De Schampheleire]

Hi Charles,

On Fri, Aug 29, 2014 at 8:22 PM, buildrootcharles
<charles.s@mercury-security.com> wrote:
> default.config
> <http://buildroot-busybox.2317881.n4.nabble.com/file/n78215/default.config>
>
>> Which version of Buildroot are you using? Is this a recent release?
>
> I'm using Buildroot version 2013.08
>
>> Also, please send us your .config so we can try to reproduce.
>
> config file attached (I renamed it default.config just for the upload)
>
>> The message 'Downloading additional patches' should not appear for
>> local patches, i.e. those that are in a directory, but only for http
>> or ftp patches.

I cannot reproduce this. Your config file looks sane as far as the
kernel settings are concerned.
I just modified the path to the kernel and patch directory, then I get:

$ make linux-dirclean
rm -Rf /tmp/buildroot-2013.08/output/build/linux-custom
tdescham at argentina /tmp/buildroot-2013.08 $ make linux-patch
>>> linux custom Download additional patches
>>> linux custom Extracting
bzcat /tmp/buildroot-2013.08/dl/linux-3.9.4.tar.bz2 | tar
--strip-components=1 -C
/tmp/buildroot-2013.08/output/build/linux-custom  -xf -
>>> linux custom Patching /package/linux
for p in /tmp/foo ; do if echo $p | grep -q -E "^ftp://|^http://" ;
then support/scripts/apply-patches.sh
/tmp/buildroot-2013.08/output/build/linux-custom
/tmp/buildroot-2013.08/dl `basename $p` ; elif test -d $p ; then
support/scripts/apply-patches.sh
/tmp/buildroot-2013.08/output/build/linux-custom $p linux-\*.patch ;
else support/scripts/apply-patches.sh
/tmp/buildroot-2013.08/output/build/linux-custom `dirname $p`
`basename $p` ; fi done

Applying linux-bar.patch using patch:
[..]

The corresponding settings were:
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="file:///tmp/linux-3.9.4.tar.bz2"
BR2_LINUX_KERNEL_PATCH="/tmp/foo"
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="/home/MSC/custom_linux-3.10.4.config"


Your config file indicates that this is not a clean buildroot tree.
Have you verified this issue on a clean buildroot-2013.08 release?
Were any changes made in this area?

If the problem is still present, you could instrument linux/linux.mk
with some echo statements, particularly in the LINUX_DOWNLOAD_PATCHES
and LINUX_APPLY_PATCHES blocks.

Best regards,
Thomas

[Buildroot] Custom kernal patch not being run

[buildrootcharles]

Thomas, 

> I cannot reproduce this. Your config file looks sane as far as the 
> kernel settings are concerned. 
> I just modified the path to the kernel and patch directory, then I get: 

> $ make linux-dirclean 
> rm -Rf /tmp/buildroot-2013.08/output/build/linux-custom 
> tdescham at argentina /tmp/buildroot-2013.08 $ make linux-patch 
> >>> linux custom Download additional patches 
> >>> linux custom Extracting 
> bzcat /tmp/buildroot-2013.08/dl/linux-3.9.4.tar.bz2 | tar 
> --strip-components=1 -C 
> /tmp/buildroot-2013.08/output/build/linux-custom  -xf - 
> >>> linux custom Patching /package/linux 
> for p in /tmp/foo ; do if echo $p | grep -q -E "^ftp://|^http://" ; 
> then support/scripts/apply-patches.sh 
> /tmp/buildroot-2013.08/output/build/linux-custom 
> /tmp/buildroot-2013.08/dl `basename $p` ; elif test -d $p ; then 
> support/scripts/apply-patches.sh 
> /tmp/buildroot-2013.08/output/build/linux-custom $p linux-\*.patch ; 
> else support/scripts/apply-patches.sh 
> /tmp/buildroot-2013.08/output/build/linux-custom `dirname $p` 
> `basename $p` ; fi done 

> Applying linux-bar.patch using patch: 
> [..] 

> The corresponding settings were: 
> BR2_LINUX_KERNEL=y 
> BR2_LINUX_KERNEL_CUSTOM_TARBALL=y 
> BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="file:///tmp/linux-3.9.4.tar.bz2" 
> BR2_LINUX_KERNEL_PATCH="/tmp/foo" 
> BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y 
> BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="/home/MSC/custom_linux-3.10.4.config" 


> Your config file indicates that this is not a clean buildroot tree. 
> Have you verified this issue on a clean buildroot-2013.08 release? 
> Were any changes made in this area? 

> If the problem is still present, you could instrument linux/linux.mk 
> with some echo statements, particularly in the LINUX_DOWNLOAD_PATCHES 
> and LINUX_APPLY_PATCHES blocks. 

> Best regards, 
> Thomas

Based on your result, I decided to re-download Buildroot-2013.08 and run make linux-patch command - no patch installed. I went in and changed my linux configuration from Kernel Version: "Custom tarball" to "3.10.10" and left all other options the same, it attempted to patch the downloaded package with the patch that I have available in my BR2_LINUX_KERNEL_PATCH directory. So I guess now the question is why would it not attempt to install the patch on my "Custom tarball"? Does Buildroot think that since it is a custom tarball that no patches will be required? (I also tried manually editing the .config to change the BR2_LINUX_KERNEL_VERSION from "custom" to "3.10.4" and it attempted to patch the kernel although I would like to have my kernel package under source control so downloading it everytime is not ideal)

WORKING .CONFIG:
#
# Kernel
#
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_LATEST_VERSION=y
# BR2_LINUX_KERNEL_SAME_AS_HEADERS is not set
# BR2_LINUX_KERNEL_CUSTOM_VERSION is not set
# BR2_LINUX_KERNEL_CUSTOM_TARBALL is not set
# BR2_LINUX_KERNEL_CUSTOM_GIT is not set
BR2_LINUX_KERNEL_VERSION="3.10.10"
BR2_LINUX_KERNEL_PATCH="/home/MSC/patch_test"
# BR2_LINUX_KERNEL_USE_DEFCONFIG is not set
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="/home/MSC/ep4502msc_linux-3.10.4.config"
BR2_LINUX_KERNEL_UBOOT_IMAGE=y
BR2_LINUX_KERNEL_UIMAGE=y
# BR2_LINUX_KERNEL_APPENDED_UIMAGE is not set
# BR2_LINUX_KERNEL_ZIMAGE is not set
# BR2_LINUX_KERNEL_APPENDED_ZIMAGE is not set
# BR2_LINUX_KERNEL_VMLINUX is not set
# BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM is not set
BR2_LINUX_KERNEL_UIMAGE_LOADADDR=""
# BR2_LINUX_KERNEL_DTS_SUPPORT is not set
# BR2_LINUX_KERNEL_INSTALL_TARGET is not set


NON-WORKING .CONFIG:
#
# Kernel
#
BR2_LINUX_KERNEL=y
# BR2_LINUX_KERNEL_LATEST_VERSION is not set
# BR2_LINUX_KERNEL_SAME_AS_HEADERS is not set
# BR2_LINUX_KERNEL_CUSTOM_VERSION is not set
BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
# BR2_LINUX_KERNEL_CUSTOM_GIT is not set
BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="file:///home/MSC/linux-3.10.4.tar.gz"
BR2_LINUX_KERNEL_VERSION="custom"
BR2_LINUX_KERNEL_PATCH="/home/MSC/patch_test"
# BR2_LINUX_KERNEL_USE_DEFCONFIG is not set
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="/home/MSC/ep4502msc_linux-3.10.4.config"
BR2_LINUX_KERNEL_UBOOT_IMAGE=y
BR2_LINUX_KERNEL_UIMAGE=y
# BR2_LINUX_KERNEL_APPENDED_UIMAGE is not set
# BR2_LINUX_KERNEL_ZIMAGE is not set
# BR2_LINUX_KERNEL_APPENDED_ZIMAGE is not set
# BR2_LINUX_KERNEL_VMLINUX is not set
# BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM is not set
BR2_LINUX_KERNEL_UIMAGE_LOADADDR=""
# BR2_LINUX_KERNEL_DTS_SUPPORT is not set
# BR2_LINUX_KERNEL_INSTALL_TARGET is not set



This transmission may contain sensitive, confidential and/or privileged
information. The sender does not waive any privilege or confidentiality in the
event of an inadvertent transmission to an unauthorized recipient. In the event
of such a transmission, please kindly contact the sender and delete all copies of
email. It is the recipient's responsibility to check this email and any
attachments for viruses. Mercury Security and the sender accept no responsibility
whatsoever for any loss suffered as a result of a virus entering the recipient's
computer system. Thank you.




--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Custom-kernal-patch-not-being-run-tp78152p78510.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140902/b803fd59/attachment.html>

[Buildroot] Custom kernal patch not being run

[Thomas De Schampheleire]

Hi Charles,

On Tue, Sep 2, 2014 at 11:32 PM, buildrootcharles
<charles.s@mercury-security.com> wrote:
> Thomas,
>
>> I cannot reproduce this. Your config file looks sane as far as the
>> kernel settings are concerned.
>> I just modified the path to the kernel and patch directory, then I get:
>
>> $ make linux-dirclean
>> rm -Rf /tmp/buildroot-2013.08/output/build/linux-custom
>> tdescham at argentina /tmp/buildroot-2013.08 $ make linux-patch
>> >>> linux custom Download additional patches
>> >>> linux custom Extracting
>> bzcat /tmp/buildroot-2013.08/dl/linux-3.9.4.tar.bz2 | tar
>> --strip-components=1 -C
>> /tmp/buildroot-2013.08/output/build/linux-custom  -xf -
>> >>> linux custom Patching /package/linux
>> for p in /tmp/foo ; do if echo $p | grep -q -E "^ftp://|^http://" ;
>> then support/scripts/apply-patches.sh
>> /tmp/buildroot-2013.08/output/build/linux-custom
>> /tmp/buildroot-2013.08/dl `basename $p` ; elif test -d $p ; then
>> support/scripts/apply-patches.sh
>> /tmp/buildroot-2013.08/output/build/linux-custom $p linux-\*.patch ;
>> else support/scripts/apply-patches.sh
>> /tmp/buildroot-2013.08/output/build/linux-custom `dirname $p`
>> `basename $p` ; fi done
>
>> Applying linux-bar.patch using patch:
>> [..]
>
>> The corresponding settings were:
>> BR2_LINUX_KERNEL=y
>> BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
>> BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="file:///tmp/linux-3.9.4.tar.bz2"
>> BR2_LINUX_KERNEL_PATCH="/tmp/foo"
>> BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
>> BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="/home/MSC/custom_linux-3.10.4.config"
>
>
>> Your config file indicates that this is not a clean buildroot tree.
>> Have you verified this issue on a clean buildroot-2013.08 release?
>> Were any changes made in this area?
>
>> If the problem is still present, you could instrument linux/linux.mk
>> with some echo statements, particularly in the LINUX_DOWNLOAD_PATCHES
>> and LINUX_APPLY_PATCHES blocks.
>
>> Best regards,
>> Thomas
>
> Based on your result, I decided to re-download Buildroot-2013.08 and run
> make linux-patch command - no patch installed. I went in and changed my
> linux configuration from Kernel Version: "Custom tarball" to "3.10.10" and
> left all other options the same, it attempted to patch the downloaded
> package with the patch that I have available in my BR2_LINUX_KERNEL_PATCH
> directory. So I guess now the question is why would it not attempt to
> install the patch on my "Custom tarball"? Does Buildroot think that since it
> is a custom tarball that no patches will be required? (I also tried manually
> editing the .config to change the BR2_LINUX_KERNEL_VERSION from "custom" to
> "3.10.4" and it attempted to patch the kernel although I would like to have
> my kernel package under source control so downloading it everytime is not
> ideal)
>

This does not make sense to me: the applying of patches is done
irrespective of whether you are using custom kernel sources or
official ones.

Could you send the output of

make linux-dirclean linux-patch V=1

using your configuration with the custom kernel (the failing one) ?

Thanks,
Thomas