From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] reminder: USE=static is *not* for libraries
Date: Wed, 30 Aug 2006 22:39:00 -0400 [thread overview]
Message-ID: <200608302239.00632.vapier@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
just found another broken package that uses the 'static' USE flag to control
generation of static libraries (aka libfoo.a)
this is very much wrong ... USE=static is only to control the static-ness of
binaries ... if your package has an option to build shared and static
libraries, then it had better be building both or you'll get smacked !
-mike
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
next reply other threads:[~2006-08-31 2:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 2:39 Mike Frysinger [this message]
2006-08-31 17:19 ` [gentoo-dev] reminder: USE=static is *not* for libraries Enrico Weigelt
2006-08-31 18:08 ` Mike Frysinger
2006-08-31 22:42 ` Doug Goldstein
2006-08-31 22:53 ` Chris White
2006-08-31 23:47 ` Mike Frysinger
2006-08-31 23:41 ` Alec Warner
2006-08-31 23:47 ` Mike Frysinger
2006-09-01 0:31 ` Alec Warner
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=200608302239.00632.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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