public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Roman Zimmermann <mereandor@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gentoo: static/dynamic linking libraries
Date: Sun, 29 Apr 2007 18:43:29 +0200	[thread overview]
Message-ID: <200704291843.33718.mereandor@gmail.com> (raw)
In-Reply-To: <20070429113659.24f0af00@snowflake>

[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]

Am Sonntag 29 April 2007 12:36 schrieb Ciaran McCreesh:
> On Sun, 29 Apr 2007 10:54:12 +0200
>
> "Jakub Moc" <jakub.moc@gmail.com> wrote:
> > On 4/29/07, Roman Zimmermann <mereandor@gmail.com> wrote:
> > > I'm now using gentoo with EXTRA_ECONF="--disable-static" for a
> > > while and it seems quite stable. Sometimes I encounter a package
> > > that won't build with this setting, but that's a rare occasion. At
> > > the moment this packages are for me:
> > > dev-libs/libpcre
> >
> > Disabling static libs in libpcre makes sys-apps/grep w/ USE=pcre bomb
> > out on compile... Just an example why you should always install both
> > of them.
>
> No, that's an example of why you should sometimes install both.

These are 5 packages out of 845 on my system. For those with version number it 
is only a compile time error, when make errornously tries to build a static 
target. Those without number are needed static by another package or don't 
like --disable-static (sys-apps/ed). That leaves 2 out of 845.
So I'm with Ciaran here: It works for almost all packages and makes at least 
some difference. Maybe enough to (really) give the users the choice (without 
the ugly EXTRA_ECONF-hack)?

Those links Jakub posted are interesting, but I don't find an explanation why 
this decission was made. Maybe you have a link to that discussion too?

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-04-29 16:48 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 [this message]
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             ` [gentoo-dev] " Kevin F. Quinn
2007-05-01  7:28               ` 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=200704291843.33718.mereandor@gmail.com \
    --to=mereandor@gmail.com \
    --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