public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] static use flag
@ 2010-12-16 13:37 Thomas Kahle
  2010-12-16 14:08 ` Mike Frysinger
  0 siblings, 1 reply; 2+ messages in thread
From: Thomas Kahle @ 2010-12-16 13:37 UTC (permalink / raw
  To: gentoo-dev

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

Hi, 

To enable the USE flags 'static' and 'static-libs' sometimes one needs
to have all of the dependencies (and maybe there dependencies) linked
statically too.  In this regard the 'static' use-flag is very different
from other use-flags in terms of its consequences and requirements.
What is the policy for ebuilds: Should they USE-depend on their
dependencies being built with static too?

If yes, there are cases where this falls short.  How would one handle
e.g. http://bugs.gentoo.org/show_bug.cgi?id=341983

app-backup/bacula needs a static glibc further down the dep chain.
Seems like out of pm's control?

Has this been discussed on gentoo-dev earlier?  Being new to devhood,
I'm looking for references.

Cheers,
Thomas


-- 
Thomas Kahle
http://dev.gentoo.org/~tomka/

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [gentoo-dev] static use flag
  2010-12-16 13:37 [gentoo-dev] static use flag Thomas Kahle
@ 2010-12-16 14:08 ` Mike Frysinger
  0 siblings, 0 replies; 2+ messages in thread
From: Mike Frysinger @ 2010-12-16 14:08 UTC (permalink / raw
  To: gentoo-dev

[-- Attachment #1: Type: Text/Plain, Size: 1220 bytes --]

On Thursday, December 16, 2010 08:37:29 Thomas Kahle wrote:
> To enable the USE flags 'static' and 'static-libs' sometimes one needs
> to have all of the dependencies (and maybe there dependencies) linked
> statically too.  In this regard the 'static' use-flag is very different
> from other use-flags in terms of its consequences and requirements.
> What is the policy for ebuilds: Should they USE-depend on their
> dependencies being built with static too?

the USE=static usage is unfortunate, but it's the best we have so far.  but 
USE=static can be thought of as a "leaf" flag ... i cant think of any reason a 
package would depend on any other being built with USE=static.

USE=static-libs however probably needs consideration in every package that 
supports USE=static.  which i think is probably what you're after.

> If yes, there are cases where this falls short.  How would one handle
> e.g. http://bugs.gentoo.org/show_bug.cgi?id=341983
> 
> app-backup/bacula needs a static glibc further down the dep chain.
> Seems like out of pm's control?

glibc always installs its static libraries.  so i dont see how it could cause 
a problem for any other package, static or otherwise.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-12-16 14:10 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-12-16 13:37 [gentoo-dev] static use flag Thomas Kahle
2010-12-16 14:08 ` Mike Frysinger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox