From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] patching issue
Date: Mon, 08 Sep 2014 12:32:29 -0300 [thread overview]
Message-ID: <540DCC0D.5080003@zacarias.com.ar> (raw)
In-Reply-To: <CAK9TtU22PKEbOF2KPRnps=oT+jt=b3rCh1zkCbqDO9rrAHyV-w@mail.gmail.com>
On 09/08/2014 11:34 AM, Sylvain LG wrote:
> Hello,
>
> I've just launched a compilation from latest buildroot sources.
>
> Here comes an issue:
>
> Applying busybox-0005-busybox-1.22.1-nc.patch using patch:
> patching file networking/nc_bloaty.c
> make: *** No rule to make target
> `package/busybox/busybox-1.22.x.config', needed by
> `/home/username/buildroot/output/build/busybox-1.22.1/.config'. Stop.
>
>
> What can I do?
Hi.
It's not a patching issue, it's a config issue.
The name of the default busybox config changed to
package/busybox/busybox.config (without the trailing version) when
multiple version support was dropped, so you need to adjust that.
Regards.
prev parent reply other threads:[~2014-09-08 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 14:34 [Buildroot] patching issue Sylvain LG
2014-09-08 15:32 ` Gustavo Zacarias [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=540DCC0D.5080003@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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