From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: ratheesh kannoth <ratheesh.ksz@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Error on building
Date: Wed, 05 Mar 2014 09:25:42 +0000 [thread overview]
Message-ID: <5316ED96.8030403@dynamicdevices.co.uk> (raw)
In-Reply-To: <CAGZFCEFFA+CBqkTbu4nsWuy4xjbbpsqrrXeLp4oE8OU84J_wkA@mail.gmail.com>
On 05/03/2014 08:01, ratheesh kannoth wrote:
> I am getting following error. what is the problem. ? How can i get around this ?
>
>
> ERROR: QA Issue: non -staticdev package contains static .a library:
> sf-test path '/work/x86_64-wrs-linux/sf/1.0-r0/packages-split/sf-test/lib/snort_dynamicengine/libsf_engine.a'
> ERROR: QA Issue: sf-test:
> /work/x86_64-wrs-linux/sf/1.0-r0/packages-split/sf-test/lib/snort_dynamicengine/libsf_engine.so.0.0.0
> contains probably-redundant RPATH /usr/lib64
>
Ratheesh, I believe you would need to ensure that any static libraries
built are either removed or packaged appropriately so as not to trigger
the Q/A error.
One approach is to modify the recipe to add the static library to the
-staticdev package, i.e. to add
FILES_${PN}-staticdev += " path\to\static\library\libsf_engine.a"
What recipe are you trying to build?
Cheers,
Alex
> Thanks,
> Ratheesh
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
represent those of the company.
next prev parent reply other threads:[~2014-03-05 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 8:01 Error on building ratheesh kannoth
2014-03-05 9:25 ` Alex J Lennon [this message]
2014-03-05 16:15 ` ratheesh kannoth
2014-03-05 16:37 ` Alex J Lennon
2014-03-05 16:54 ` ratheesh kannoth
2014-03-05 17:01 ` Alex J Lennon
2014-03-05 17:03 ` ratheesh kannoth
2014-03-05 17:10 ` Alex J Lennon
2014-03-05 21:22 ` Khem Raj
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=5316ED96.8030403@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=ratheesh.ksz@gmail.com \
--cc=yocto@yoctoproject.org \
/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.