From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: libcap_1.10: ERROR: QA Issue with libcap: non -dev package contains symlink .so
Date: Sun, 09 Jan 2011 10:20:21 -0800 [thread overview]
Message-ID: <4D29FC65.9010608@gmail.com> (raw)
In-Reply-To: <1294585014.4036.47.camel@mattotaupa>
On 1/9/2011 6:56 AM, Paul Menzel wrote:
> Dear OE folks,
>
>
> doing `bitbake -k libcap` with latest master (3d030f) with
> `minimal-uclibc` for `MACHINE = "beagleboard"`
>
> NOTE: package libcap-1.10-r2: task do_qa_staging: Succeeded
> ERROR: QA Issue with libcap: non -dev package contains symlink .so: libcap path '/work/armv7a-oe-linux-uclibceabi/libcap-1.10-r2/packages-split/libcap/usr/lib/libcap.so'
> ERROR: QA Issue with libcap: non -dev package contains symlink .so: libcap path '/work/armv7a-oe-linux-uclibceabi/libcap-1.10-r2/packages-split/libcap/usr/lib/libcap.so'
> NOTE: package libcap-1.10-r2: task do_package: Succeeded
>
> Is that error reasonable or are library packages not allowed to have
> symlinks [1]?
Usually sylinks are needed for debugging and linking thats why its
preferred in -dev packages. But you can sort it out by removing the
below lines and see how the automatic package puts stuff
>
> FILES_${PN} = "${libdir}"
> FILES_${PN}-dev = "${includedir}"
>
>
> Thanks,
>
> Paul
>
>
> [1] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/libcap/libcap_1.10.bb?id=3d030ffa57af27275fbb42eaa0fcd611f4925348
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2011-01-09 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 14:56 libcap_1.10: ERROR: QA Issue with libcap: non -dev package contains symlink .so Paul Menzel
2011-01-09 18:20 ` Khem Raj [this message]
2011-01-10 11:39 ` [PATCH] libcap, libcap2: use automatic packaging to fix QA errors Paul Menzel
2011-01-10 13:44 ` Rolf Leggewie
2011-01-10 14:45 ` Paul Menzel
2011-01-10 21:11 ` Dirk Opfer
2011-01-10 21:15 ` Dirk Opfer
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=4D29FC65.9010608@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox