From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id B766A1387FD for ; Wed, 26 Mar 2014 16:23:49 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C6A88E0BCC; Wed, 26 Mar 2014 16:23:44 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id BA027E0BB3 for ; Wed, 26 Mar 2014 16:23:43 +0000 (UTC) Received: from [192.168.1.195] (CPE002401f30b73-CM001cea3ddad8.cpe.net.cable.rogers.com [99.224.181.112]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: axs) by smtp.gentoo.org (Postfix) with ESMTPSA id 8BEC433FC21 for ; Wed, 26 Mar 2014 16:23:42 +0000 (UTC) Message-ID: <5332FF19.1030707@gentoo.org> Date: Wed, 26 Mar 2014 12:23:53 -0400 From: Ian Stakenvicius User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: crossdev and multilib interference References: <53208139.2040509@gentoo.org> <1655097.HpObVGm6RL@vapier> <20140326122529.GA19156@rathaus.eclipse.co.uk> <1660834.UE1ARX9orZ@vapier> In-Reply-To: <1660834.UE1ARX9orZ@vapier> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 1b07399c-e7ce-4ec8-afd6-392ec11aeb16 X-Archives-Hash: 1df0d340eb3ff4992f9f24f91f2cbcb3 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 26/03/14 12:12 PM, Mike Frysinger wrote: > On Wed 26 Mar 2014 12:25:29 Steven J. Long wrote: >> Mike Frysinger wrote: >>> Greg Turner wrote: >>>> As for how to fix it, if foo-bar-baz-quux crossdev targets >>>> are at ${EROOT}/usr/foo-bar-baz-quux, putting wrappers in >>>> ${EROOT}/usr/foo-bar-baz-quux/cross-wrappers, or something >>>> like that, seems perfectly reasonable... heck, pure >>>> speculation, but it might even noticeably speed up day-to-day >>>> $PATH searching on systems with lots of crossdev targets >>>> installed. >>> >>> if they're in $PATH, then the exact location is irrelevant. >>> they need not be in /usr/bin to cause a problem. if they're not >>> in $PATH, then you're breaking the cross-compilers and that is >>> unacceptable. >> >> Cross-compilation should be supported via cross-emerge, and >> perhaps a small script the cross-compiler sources to setup the >> env (ie prefix to PATH in this case) for using CHOST-* tools, >> like x86-pc-linux-gnu-gcc targetting a straight x86 platform, >> instead of the normal multilib setup. The latter being used by >> the former (I'd have thought it was already done.) >> >> The cross tools should NOT pollute the default PATH, simply >> because the user happened to run crossdev at some point. It's >> *borked*, plain and simple, so fix it please or expect people to >> come up with other solutions [1]; fragmenting the effort, and >> making cross-compilers lives harder, as we try to blend together >> a working solution from various efforts. The exact thing crossdev >> is supposed to answer. > > that's bs. people install crossdev to get a cross-compile > environment, not to get something that only works through `emerge`. > attempting to restrict it so it only works through `emerge` is > unacceptable and it has never been that way. -mike > it -does- make sense though to limit anything that one wants to EMERGE with the crossdev, to require the use of cross-emerge. Would it not be possible to somehow ensure the crossdev tools are ignored in/removed from/cannot pollute the standard emerge environment? Are there any use cases where one -would- want the crossdev to be used in a standard emerge environment instead of using cross-emerge ? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlMy/xkACgkQ2ugaI38ACPClAAD/bwSIWjCu32eDlf3faqnqhvc3 94JxKfSwY3pPv7X4A68A/1g8KSov5e/BHGYXyhlyCd8j3Bc+IukxoNYMXiXiluh7 =TMGw -----END PGP SIGNATURE-----