public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] USE flags and static libs
Date: Sat, 08 Jun 2002 15:16:40 +0200	[thread overview]
Message-ID: <157640000.1023542200@krabat.ahsoftware> (raw)

Hi,

I like brainstorming. ;)

I've mentioned it before as a remark in another msg, I would find it nice 
to have a USE flag tests mentioned in the documentation. This could inspire 
some developers to call 'make tests' or similiar before installing if 
something is provided by the makefile of the package.

I also want to discuss the building of static libs. Right now all or most 
of the static libs are build with the flags from make.conf. The problem 
with that is that this prevents building binaries (which uses them) to give 
away (or for using on other machines). E.g. a binary build with march=i686 
won't run on k6.

This could lead to some 'hard to find' problems if someone forgets this.

I've two aproaches to this problem:

1. Building all static libs without march flags.

2. Introduce a USE flag i386static
This could be used to build additional static libs with a postfix i386. 
E.g.
libncurses.a and libncurses_i386.a.

I would prefer the second approach. Like the USE flag 'tests', just 
describing it in the appropriate developer docs could be enough to get that 
into (some) future ebuilds.

Comments?


Regards,

Alexander



             reply	other threads:[~2002-06-08 13:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-08 13:16 Alexander Holler [this message]
2002-06-08 13:49 ` [gentoo-dev] USE flags and static libs Alexander Holler
2002-06-08 15:00 ` Alexander Gretencord

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=157640000.1023542200@krabat.ahsoftware \
    --to=holler@ahsoftware.de \
    --cc=gentoo-dev@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