Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Sagaert <sagaert.johan@proximus.be>
To: buildroot@busybox.net
Subject: [Buildroot] patch: **** Only garbage was found in the patch input.
Date: Wed, 9 Mar 2016 11:46:58 +0100	[thread overview]
Message-ID: <56DFFF22.4060207@proximus.be> (raw)
In-Reply-To: <871t7k41b9.fsf@dell.be.48ers.dk>

Hi Peter ,

Op 9/03/2016 om 7:23 schreef Peter Korsgaard:
>>>>>> "Johan" == Johan Sagaert<sagaert.johan@proximus.be>  writes:
>   > Hi
>   > Applying 0001-logo.patch using patch:
>   > patch: **** Only garbage was found in the patch input.
>   > Patch failed!  Please fix 0001-logo.patch!
>
>   > I always use  git format patch to create patches  to use them
>   > as usual in buildroot.
>   > The modified files where image files, so this yields a binary patch.
>
>   > It looks like patch does not understand the binary format that git
>   > format patch creates.
>
> Indeed, gnu patch afaik doesn't support the binary git diff format.
>
>   > Is there any workaround this or do i have to revert to the old diff
>   > method for making patches
>   > of non text files ?
>
> Is this patch really something that is needed to fix a build issue of
> the package? From the file name it more sounds like som project specific
> customization of the rootfs. If that is so, why not just include the
> image in your rootfs overlay?
>
I have to replace a logo bitmap in the u-boot sources that are pulled 
from a git repository .
So  i will have to add a |PRE_BUILD_HOOK for the u-boot loader in this 
case to replace the
logo bmp file before building, since diff cant create patches of binary 
files.

Regards, Johan



|
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160309/077f46c8/attachment.html>

  reply	other threads:[~2016-03-09 10:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 23:59 [Buildroot] patch: **** Only garbage was found in the patch input Johan Sagaert
2016-03-09  6:23 ` Peter Korsgaard
2016-03-09 10:46   ` Johan Sagaert [this message]
2016-03-09 10:51     ` Peter Korsgaard

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=56DFFF22.4060207@proximus.be \
    --to=sagaert.johan@proximus.be \
    --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