From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] Fix compilation of busybox 1.21.1
Date: Wed, 09 Oct 2013 15:51:42 +0200 [thread overview]
Message-ID: <87fvsa3635.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <4032860.0r4xX98ikO@sagittae> ("Jérôme Pouiller"'s message of "Wed, 09 Oct 2013 15:47:59 +0200")
>>>>> "J?r?me" == J?r?me Pouiller <jezz@sysmic.org> writes:
J?r?me> On Wednesday 09 October 2013 11:15:09 J?r?me Pouiller wrote:
>> It seems patches previously applied on busybox 1.20.2 are also needed
>> for version 1.21.1.
>>
>> Signed-off-by: J?r?me Pouiller <jezz@sysmic.org>
>> ---
>> ...ersion_code-don-t-fail-on-Linux-version-s.patch | 46 ++++++++
>> ...correct-m_status-field-in-outgoing-packet.patch | 40 +++++++
>> .../1.21.1/busybox-1.21.1-pkg-config-selinux.patch | 67 +++++++++++
>> .../1.21.1/busybox-1.21.1-sys-resource.patch | 123 ++++++++++++++++++++
>> 4 files changed, 276 insertions(+)
>> create mode 100644 package/busybox/1.21.1/busybox-1.21.1-get_linux_version_code-don-t-fail-on-Linux-version-s.patch
>> create mode 100644 package/busybox/1.21.1/busybox-1.21.1-ntpd-fix-incorrect-m_status-field-in-outgoing-packet.patch
>> create mode 100644 package/busybox/1.21.1/busybox-1.21.1-pkg-config-selinux.patch
>> create mode 100644 package/busybox/1.21.1/busybox-1.21.1-sys-resource.patch
J?r?me> Arg! Forget this patch. Problem was local to my workstation.
Ahh, ok - I was just about to ask why these patches were needed.
J?r?me> Sorry for disturbing,
No problem, I'll remove them from patchwork.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-10-09 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 9:15 [Buildroot] [PATCH v2] Fix compilation of busybox 1.21.1 Jérôme Pouiller
2013-10-09 13:47 ` Jérôme Pouiller
2013-10-09 13:51 ` Peter Korsgaard [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=87fvsa3635.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.