From: "Kevin F. Quinn" <kevquinn@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gentoo: static/dynamic linking libraries
Date: Mon, 30 Apr 2007 21:00:27 +0200 [thread overview]
Message-ID: <20070430210027.128dc96b@c1358217.kevquinn.com> (raw)
In-Reply-To: <200704300507.10429.mereandor@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
On Mon, 30 Apr 2007 05:07:00 +0200
Roman Zimmermann <mereandor@gmail.com> wrote:
> Am Montag 30 April 2007 00:11 schrieb Ciaran McCreesh:
> > On Sun, 29 Apr 2007 14:56:57 -0700
> >
> > Donnie Berkholz <dberkholz@gentoo.org> wrote:
> > > Anyone who wants to build a static binary wants the static libs.
> > > Given the difficulty in universally enabling or disabling their
> > > builds because of build-system differences, building them and
> > > tossing them in the trash with INSTALL_MASK, as Marius suggested,
> > > seems like the best way to go.
> >
> > The best way to go or the only viable short term solution?
Best way to go, IMO.
> That's the point! Universally disabling static builds can't be a
> longterm solution. The only sane way to do this is on a per ebuild
> basis.
The thing about static libraries, is that the ebuild that creates them
doesn't know whether anything else will want to use them. It may be
that in practice, most libraries are never used in their static form -
but the point is that the ebuild doesn't know enough information to
make the decision.
However, with INSTALL_MASK, the user makes the decision never to have
static binaries, and thus gets a system free of static libraries.
--
Kevin F. Quinn
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-30 19:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-29 8:32 [gentoo-dev] gentoo: static/dynamic linking libraries Roman Zimmermann
2007-04-29 8:54 ` Jakub Moc
2007-04-29 10:36 ` Ciaran McCreesh
2007-04-29 16:43 ` Roman Zimmermann
2007-04-29 17:50 ` Marius Mauch
2007-04-29 17:56 ` Ciaran McCreesh
2007-04-29 18:21 ` Roman Zimmermann
2007-04-29 18:46 ` paul kölle
2007-04-29 19:04 ` Roman Zimmermann
2007-04-29 19:31 ` Marius Mauch
2007-04-29 19:36 ` Ciaran McCreesh
2007-04-29 20:05 ` Olivier Crête
2007-04-29 21:50 ` Rémi Cardona
2007-04-29 21:56 ` Donnie Berkholz
2007-04-29 22:11 ` Ciaran McCreesh
2007-04-30 3:07 ` Roman Zimmermann
2007-04-30 3:35 ` Marius Mauch
2007-04-30 7:28 ` Roman Zimmermann
2007-04-30 8:49 ` [gentoo-dev] " Duncan
2007-04-30 19:00 ` Kevin F. Quinn [this message]
2007-05-01 7:28 ` [gentoo-dev] " Roman Zimmermann
2007-05-01 2:49 ` Peter Gordon
2007-05-01 5:16 ` Donnie Berkholz
2007-05-01 9:16 ` Radoslaw Stachowiak
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=20070430210027.128dc96b@c1358217.kevquinn.com \
--to=kevquinn@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