From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] knock: Fix build failure due to missing README file.
Date: Thu, 12 Dec 2013 15:27:01 +0100 [thread overview]
Message-ID: <871u1i2lhm.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1386851218-19360-1-git-send-email-Vincent.Riera@imgtec.com> (Vicente Olivert Riera's message of "Thu, 12 Dec 2013 12:26:58 +0000")
>>>>> "Vicente" == Vicente Olivert Riera <Vincent.Riera@imgtec.com> writes:
> Apply upstream patch: 306a696c0882f28a5cd2e41d392c3a6ed14d45f4
> The build process fails because Makefile.am includes README as part of
> the documentation files, but actually it doesn't exist:
> make[2]: *** No rule to make target `README', needed by `all-am'. Stop.
> The right file is README.md, so making that replacement to Makefile.am
> fixes the problem.
Ups, houston we have a problem:
>>> knock 7666f2e86e18d482eaad5fe1fea46d87d80b0555 Downloading
--2013-12-12 15:09:21-- https://github.com/jvinet/knock/tarball/master/knock-7666f2e86e18d482eaad5fe1fea46d87d80b0555.tar.gz
Resolving github.com (github.com)... 192.30.252.129
Connecting to github.com (github.com)|192.30.252.129|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/jvinet/knock/legacy.tar.gz/master [following]
--2013-12-12 15:09:22-- https://codeload.github.com/jvinet/knock/legacy.tar.gz/master
Resolving codeload.github.com (codeload.github.com)... 192.30.252.144
Connecting to codeload.github.com (codeload.github.com)|192.30.252.144|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: `/var/lib/downloads/knock-7666f2e86e18d482eaad5fe1fea46d87d80b0555.tar.gz.tmp'
[ <=> ] 27,846 --.-K/s in 0.001s
2013-12-12 15:09:23 (41.6 MB/s) - `/var/lib/downloads/knock-7666f2e86e18d482eaad5fe1fea46d87d80b0555.tar.gz.tmp' saved [27846]
>>> knock 7666f2e86e18d482eaad5fe1fea46d87d80b0555 Extracting
gzip -d -c /var/lib/downloads/knock-7666f2e86e18d482eaad5fe1fea46d87d80b0555.tar.gz | tar --strip-components=1 -C /home/peko/source/buildroot/output/build/knock-7666f2e86e18d482eaad5fe1fea46d87d80b0555 -xf -
>>> knock 7666f2e86e18d482eaad5fe1fea46d87d80b0555 Patching
Applying knock-001-Fix-missing-README-file.patch using patch:
patching file Makefile.am
Reversed (or previously applied) patch detected! Skipping patch.
The github URL was wrong, so it always downloaded the latest version
from master.
With that fixed the patch is not needed (as the README -> README.md
rename only happeneded after 7666f2):
https://github.com/jvinet/knock/commit/4faa1daa4f8ab6825a2becf106f43220af395132
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-12-12 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 12:26 [Buildroot] [PATCH v3] knock: Fix build failure due to missing README file Vicente Olivert Riera
2013-12-12 14:27 ` Peter Korsgaard [this message]
2013-12-12 22:29 ` Arnout Vandecappelle
2013-12-12 22:50 ` Peter Korsgaard
2013-12-13 9:33 ` Vicente Olivert Riera
2013-12-13 9:58 ` Peter Korsgaard
2013-12-16 14:39 ` Vicente Olivert Riera
2013-12-16 15:14 ` Peter Korsgaard
2013-12-16 15:46 ` Vicente Olivert Riera
2013-12-16 15:50 ` Vicente Olivert Riera
2013-12-16 15:55 ` Peter Korsgaard
2013-12-16 16:38 ` Vicente Olivert Riera
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=871u1i2lhm.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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