From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Using global patch dir to patch "host-*" packages from buildroot
Date: Tue, 23 Aug 2016 10:32:02 +0200 [thread overview]
Message-ID: <20160823083202.GA5749@free.fr> (raw)
In-Reply-To: <CADj18OXZwbD+eL1dR2_n6W_uovwgeV48GTJvHQ3rpTRCGQed1w@mail.gmail.com>
Pascal, All,
On 2016-08-23 07:12 +0000, Pascal K spake thusly:
> Hello everyone,
>
> I tried to upgrade my build system from gcc 4.9 to 6. So far only a few
> patches are needed.
> All of those patches have to be in packages for the host.
>
> So my question is how to keep those patches out of my clean checkout of
> buildroot?
Patches can only be applied to packages sources, not to Buildroot
itself.
> If I set the global patch dir and put the patch e.g. for ucl-1.03 into this
> dir, the mk file I was about to patch is not found. I am not sure how to
> configure the path to point to the host-ucl-1.03.
>
> *Here the build error that occurs:*
>
> >>> host-ucl 1.03 Patching
>
> Applying 0002-gcc6-build-fix.patch using patch:
> can't find file to patch at input line 3
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |--- a/ucl.mk
> |+++ b/ucl.mk
> --------------------------
> No file to patch. Skipping patch.
> 1 out of 1 hunk ignored
> Patch failed! Please fix 0002-gcc6-build-fix.patch!
>
>
> *My Patch: *
> --- a/ucl.mk
> +++ b/ucl.mk
> @@ -9,4 +9,7 @@
> UCL_LICENSE = GPLv2+
> UCL_LICENSE_FILES = COPYING
>
> +# Fix ACC conformance test failure for host gcc 6.xx
> +HOST_UCL_CONF_ENV += CPPFLAGS="$(HOST_CPPFLAGS) -std=c90"
> +
> $(eval $(host-autotools-package))
>
> *Folder with the patch:*
> ../Develop/EmbeddedLinux/emblx/board/IPETRONIK/common/patches/ucl/
> *Folder to apply the patch to:*
> ../Develop/EmbeddedLinux/emblx/buildroot/package/ucl/
>
> Any suggestions?
Patch Buildroot itself and send us the patches! ;-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2016-08-23 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 7:12 [Buildroot] Using global patch dir to patch "host-*" packages from buildroot Pascal K
2016-08-23 8:32 ` Yann E. MORIN [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=20160823083202.GA5749@free.fr \
--to=yann.morin.1998@free.fr \
--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