From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1FyVi7-0003TN-JE for garchives@archives.gentoo.org; Thu, 06 Jul 2006 15:24:12 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k66FNE5l011562; Thu, 6 Jul 2006 15:23:14 GMT Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k66FKrdx023753 for ; Thu, 6 Jul 2006 15:20:53 GMT Received: from [172.23.170.145] (helo=anti-virus03-08) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1FyVev-0000hV-3v for gentoo-dev@lists.gentoo.org; Thu, 06 Jul 2006 16:20:53 +0100 Received: from [82.41.57.20] (helo=snowdrop.home) by asmtp-out2.blueyonder.co.uk with esmtpa (Exim 4.52) id 1FyVeu-0000Np-0h for gentoo-dev@lists.gentoo.org; Thu, 06 Jul 2006 16:20:52 +0100 Date: Thu, 6 Jul 2006 16:20:48 +0100 From: Ciaran McCreesh To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Replacing cpu-feature USE flags Message-ID: <20060706162048.7063e572@snowdrop.home> In-Reply-To: <44AD27B6.4010008@gentoo.org> References: <200607061252.33028@enterprise.flameeyes.is-a-geek.org> <20060706131905.3ba12b49@snowdrop.home> <200607061429.39803@enterprise.flameeyes.is-a-geek.org> <20060706134939.6ecd7758@snowdrop.home> <44AD1843.1090707@gentoo.org> <20060706151655.1edaa10f@snowdrop.home> <44AD27B6.4010008@gentoo.org> X-Mailer: Sylpheed-Claws 2.3.1 (GTK+ 2.8.19; i686-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 2eaf6765-6dc0-4d1b-9fc9-506145f9599d X-Archives-Hash: 4cf156d10b8688ad95edaa250702db9e On Thu, 06 Jul 2006 17:09:42 +0200 Simon Stelling wrote: | Ciaran McCreesh wrote: | > You can do it through bashrc. But then, if this is about working | > around Portage's annoying lack of sane cross compile handling, why | > not put a little effort into fixing it properly rather than a lot | > of effort into making the tree more complicated? | | Err, I think you're mixing up different things. How should portage be | able to do sane cross compiling if you control the instruction sets | through use flags which are blocked in profiles the build system is | using? That's just it. You shouldn't be using the wrong profile when compiling things. | In fact, moving away from use flags over to the real(TM) | solution is a step towards fixing the issue. Also, it doesn't make | the tree more complicated. It is far more intuitive that supported | instruction sets are used if the user doesn't explicitly wish not to | than having some strange use flags that don't mean what they're named | like. That's like saying "well we should just link against whatever's available, it's far more intuitive than letting the user decide". -- Ciaran McCreesh Mail : ciaran dot mccreesh at blueyonder.co.uk -- gentoo-dev@gentoo.org mailing list