Re: [gentoo-dev] Re: crossdev and multilib interference

[Ian Stakenvicius <axs@gentoo.org>]

-----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-----