From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/opencv3: fix aarch64 build
Date: Tue, 31 Jul 2018 07:19:00 +0200 [thread overview]
Message-ID: <43853fxp6j.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20180730235001.429c059e@windsurf
Hi Thomas,
Am Mon, 30 Jul 2018 23:50:01 +0200 schrieb Thomas Petazzoni:
> So this fix is already needed with the currently packaged 3.3.0 version
> of OpenCV ?
yes: http://autobuild.buildroot.net/?reason=opencv3-3.3.0
Please note that the aarch64 build errors started on June 9th, 2018.
> If so, why is this fix patch coming *after* the version bump in the
> series ?
OpenCV 3.4.2 is also affected by the problem, because of that I think
that patch order does not matter. My first try to fix the build error was
to bump package version, seeing that this did not fix the problem I
investigated further and found the VFPV3 problem.
> Both 2018.05.x and 2018.02.x are using 3.3.0, so I guess they are
> affected as well. However, this failure doesn't appear for 2018.02.x and
> 2018.05.x in http://autobuild.buildroot.net/?reason=opencv3%
>
> Do you have an explanation for this ?
The bug was introduced by https://git.buildroot.net/buildroot/commit/
package/opencv3?id=a17402e42d8c996af239cfdb536e74188d6c6245 on June 7th,
2018. This patch was only committed to the master branch.
Regards, Bernd
next prev parent reply other threads:[~2018-07-31 5:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 16:08 [Buildroot] [PATCH 1/2] package/opencv3: bump version to 3.4.2 Bernd Kuhls
2018-07-30 16:08 ` [Buildroot] [PATCH 2/2] package/opencv3: fix aarch64 build Bernd Kuhls
2018-07-30 21:50 ` Thomas Petazzoni
2018-07-31 5:19 ` Bernd Kuhls [this message]
2018-07-31 20:08 ` Thomas Petazzoni
2018-07-31 20:08 ` Thomas Petazzoni
2018-07-31 20:09 ` [Buildroot] [PATCH 1/2] package/opencv3: bump version to 3.4.2 Thomas Petazzoni
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=43853fxp6j.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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