From: Steffen Sledz <sledz@dresearch-fe.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <Openembedded-devel@lists.openembedded.org>
Subject: Re: opencv QA issue
Date: Tue, 28 Jan 2014 09:09:47 +0100 [thread overview]
Message-ID: <52E765CB.3090600@dresearch-fe.de> (raw)
In-Reply-To: <CAMKF1srbr9PCgJSbmXLFTPcMxsEwno7EUAKqc-ADzbiO1DU6kw@mail.gmail.com>
On 27.01.2014 17:29, Khem Raj wrote:
> On Mon, Jan 27, 2014 at 8:18 AM, Steffen Sledz <sledz@dresearch-fe.de> wrote:
>> After the latest update of our build host (Fedora-18) the opencv build fails with an QA issue.
>>
>> -------------> snip <-------------
>> ERROR: QA Issue: non debug package contains .debug directory: opencv-apps path /work/cortexa9hf-vfp-neon-angstrom-linux-gnueabi/opencv/2.4.6+gitAUTOINC+c5afaa4e8d-r0/packages-split/opencv-apps/usr/share/OpenCV/java/.debug/libopencv_java246.so
>> WARNING: QA Issue: opencv-apps: found library in wrong location: /usr/share/OpenCV/java/libopencv_java246.so
>> opencv-apps: found library in wrong location: /usr/share/OpenCV/java/.debug/libopencv_java246.so
>> ERROR: QA run found fatal errors. Please consider fixing them.
>> ERROR: Function failed: do_package_qa
>> ERROR: Logfile of failure stored in: /CACHE/jenkins-workspace/hipos-dfe-closed/build-closed/tmp-eglibc/work/cortexa9hf-vfp-neon-angstrom-linux-gnueabi/opencv/2.4.6+gitAUTOINC+c5afaa4e8d-r0/temp/log.do_package.15005
>> NOTE: recipe opencv-2.4.6+gitAUTOINC+c5afaa4e8d-r0: task do_package: Failed
>> ERROR: Task 502 (/CACHE/jenkins-workspace/hipos-dfe-closed/meta-openembedded/meta-oe/recipes-support/opencv/opencv_2.4.bb, do_package) failed with exit code '1'
>> -------------> snap <-------------
>>
>> After some research we found that the libopencv_java246.so wasn't build before the mentioned build host update. I'm not a cmake guru, so i can't determine why it is build after this update.
>>
>> But it seems to be clear that the path /usr/share/OpenCV/java/.debug/libopencv_java246.so is not covered by the package-split definition in meta-oe/recipes-support/opencv/opencv_2.4.bb:
>>
>> -------------> snip <-------------
>> FILES_${PN} = ""
>> FILES_${PN}-apps = "${bindir}/* ${datadir}/OpenCV"
>> FILES_${PN}-dbg += "${libdir}/.debug"
>
> it should be added like something below
>
> FILES_${PN}-dbg += "${datadir}/OpenCV/java/.debug"
>
> can you try it out if it fixes the problem.
The error is gone. But there's still a QA warning.
-------------> snip <-------------
WARNING: QA Issue: opencv-apps: found library in wrong location: /usr/share/OpenCV/java/libopencv_java246.so
opencv-dbg: found library in wrong location: /usr/share/OpenCV/java/.debug/libopencv_java246.so
-------------> snap <-------------
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next prev parent reply other threads:[~2014-01-28 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52E686D4.4040906@dresearch-fe.de>
2014-01-27 16:29 ` opencv QA issue Khem Raj
2014-01-28 8:09 ` Steffen Sledz [this message]
2014-01-28 8:20 ` Henning Heinold
2014-01-28 9:08 ` Stefan Herbrechtsmeier
2014-02-11 12:09 ` Steffen Sledz
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=52E765CB.3090600@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=Openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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