From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Buildroot} [PATCH] Remove qt5base explicitlib patch
Date: Tue, 6 Sep 2016 21:35:41 +0200 [thread overview]
Message-ID: <20160906213541.39feefc1@free-electrons.com> (raw)
In-Reply-To: <20160906192831.67fde478@gmx.net>
Hello,
On Tue, 6 Sep 2016 19:28:31 +0200, Peter Seiderer wrote:
> I think something went wrong with your update to latest master because
> the patch 'package/qt5/qt5base/0007-build-with-explicitlib-after-all.patch'
> was already removed as part of the version bump to 5.6.1-1, see commit
> 'qt5: bump version to 5.6.1-1' ([1])...
I confirm: qt5base patches apply just fine here:
>>> qt5base 5.6.1-1 Extracting
xzcat /home/thomas/dl/qtbase-opensource-src-5.6.1-1.tar.xz | tar --strip-components=1 -C /home/thomas/projets/buildroot/output/build/qt5base-5.6.1-1 -xf -
>>> qt5base 5.6.1-1 Patching
Applying 0006-eglfs-rasp-pi-header-inclusion.patch using patch:
patching file config.tests/qpa/eglfs-brcm/eglfs-brcm.pro
patching file src/plugins/platforms/eglfs/eglfs-plugin.pro
Hunk #1 succeeded at 1 with fuzz 1 (offset -5 lines).
Applying 0007-Remove-libudev-dependency-from-kms.pro.patch using patch:
patching file config.tests/qpa/kms/kms.pro
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-06 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 14:25 [Buildroot] [Buildroot} [PATCH] Remove qt5base explicitlib patch Danijel Tudek
2016-09-06 17:28 ` Peter Seiderer
2016-09-06 19:35 ` Thomas Petazzoni [this message]
2016-09-07 13:30 ` Danijel Tudek
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=20160906213541.39feefc1@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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.