From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DMARC_MISSING, MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=4.0.0 Received: from moutvdom00.kundenserver.de (moutvdom00.kundenserver.de [195.20.224.149]) by chiba.3jane.net (Postfix) with ESMTP id 29AEDABD53 for ; Sat, 8 Jun 2002 08:15:56 -0500 (CDT) Received: from [172.19.20.62] (helo=mrvdomng1.kundenserver.de) by moutvdom00.kundenserver.de with esmtp (Exim 2.12 #3) id 17Gg4R-0006Q8-00 for gentoo-dev@gentoo.org; Sat, 8 Jun 2002 15:15:55 +0200 Received: from [217.85.222.2] (helo=eiche.ahsoftware) by mrvdomng1.kundenserver.de with esmtp (Exim 3.22 #2) id 17Gg4Q-00007e-00 for gentoo-dev@gentoo.org; Sat, 08 Jun 2002 15:15:54 +0200 Received: from krabat.ahsoftware (krabat.ahsoftware [192.168.207.2]) by eiche.ahsoftware (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id g58DDJ301223 for ; Sat, 8 Jun 2002 15:13:19 +0200 Date: Sat, 08 Jun 2002 15:16:40 +0200 From: Alexander Holler To: gentoo-dev@gentoo.org Message-ID: <157640000.1023542200@krabat.ahsoftware> X-Mailer: Mulberry/2.1.0 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: [gentoo-dev] USE flags and static libs Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 2cde7fe6-ca71-4e98-9e9a-4383c5220262 X-Archives-Hash: 69b39eb9730d5ad653afa09039cddf71 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