From: Phil Blundell <philb@gnu.org>
To: Colin Walters <walters@verbum.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] util-linux: Remove static libraries from -dev packages
Date: Tue, 25 Sep 2012 23:00:31 +0100 [thread overview]
Message-ID: <1348610431.1335.11.camel@x121e.pbcl.net> (raw)
In-Reply-To: <1348610357.2853.5.camel@lenny>
On Tue, 2012-09-25 at 17:59 -0400, Colin Walters wrote:
> On Tue, 2012-09-25 at 13:54 +0100, Phil Blundell wrote:
> > Fixes the QA warnings:
> >
> > WARNING: QA Issue: non -staticdev package contains static .a library: util-linux-libblkid-dev path '/work/mips32el-oe-linux/util-linux/2.21.2-r3micro3/packages-split/util-linux-libblkid-dev/lib/libblkid.a'
> > WARNING: QA Issue: non -staticdev package contains static .a library: util-linux-libuuid-dev path '/work/mips32el-oe-linux/util-linux/2.21.2-r3micro3/packages-split/util-linux-libuuid-dev/lib/libuuid.a'
>
> > -FILES_util-linux-libblkid-dev = "${base_libdir}/libblkid.so ${base_libdir}/libblkid.a ${base_libdir}/libblkid.la ${includedir}/blkid ${libdir}/pkgconfig/blkid.pc"
> > +FILES_util-linux-libblkid-dev = "${base_libdir}/libblkid.so ${base_libdir}/libblkid.la ${includedir}/blkid ${libdir}/pkgconfig/blkid.pc"
>
> Wouldn't EXTRA_OECONF += " --disable-static" be better?
That'd be inconsistent with other packages, since we do generally build
and ship the static libraries. Having a big switch to turn off static
libraries globally seems like a fine plan, but I can't see any obvious
reason why the util-linux ones are any more useless than the rest.
p.
next prev parent reply other threads:[~2012-09-25 22:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 12:54 [PATCH] util-linux: Remove static libraries from -dev packages Phil Blundell
2012-09-25 21:59 ` Colin Walters
2012-09-25 22:00 ` Phil Blundell [this message]
2012-09-25 22:11 ` Colin Walters
2012-09-26 8:49 ` Richard Purdie
2012-09-26 9:28 ` Phil Blundell
2012-09-26 14:05 ` Richard Purdie
2012-09-30 16:22 ` Phil Blundell
2012-09-26 14:50 ` Mark Hatle
2012-09-27 15:42 ` Saul Wold
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=1348610431.1335.11.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=walters@verbum.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.