-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 19/06/14 05:20 PM, Steven J. Long wrote:
> On Tue, Jun 17, 2014 at 10:56 -0400, Alexandre Rostovtsev wrote:
>> All multilib packages that use pkgconfig, for one thing. (Which
>> means almost all multilib packages.) Because current crossdev
>> versions blindly install their
>> /usr/bin/i686-pc-linux-gnu-pkg-config wrapper script, overwriting
>> the binary belonging to pkgconfig[abi_x86_32].
>
> Well I've spent far too long at crossdev code, only to see this and
> realise you can simply hard-mask:
> cross-i686-pc-linux-gnu/{binutils,gcc,glibc,pkg-config} in the
> amd64 multilib profile, unless I'm missing something. You'd be
> hard-pushed to install a clashing crossdev with such a mask,
> afaict.
>
> If you do want to change crossdev[1], afaict you're looking at
> interaction between toolchain.eclass (and toolchain-binutils, and
> likely -funcs), crossdev and gcc-config. I could well be wrong, as
> ever. This is just my preliminary understanding, and maybe it'll
> provoke a more thorough explanation. [ Snip! ]
Thank you for the explanation and research!
Tangental to this, mgorny wrote a little tool yesterday that might
work well as an alternative to crossdev for multilib systems. It
simply wraps all the native toolchain calls with proper -m and
provides the new CTARGETs.
If anybody wants to take a look, this is the link he posted on -dev :
http://git.overlays.gentoo.org/gitweb/?p=dev/mgorny.git;a=blob;f=sys-devel/multilib-gcc-wrapper/multilib-gcc-wrapper-0.ebuild;h=3e304313c0812ffc7da79603e38979fc81a83081;hb=HEAD
Whether or not this suits everyone's needs for an i686 crossdev on
amd64 systems, i don't know. Thoughts?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iF4EAREIAAYFAlOklU4ACgkQ2ugaI38ACPBBawD/aRIYx3q5RcSom87YWKCUf6SL
jXyavRbB1g5hP8S6B1wBAMBYvZABlKiZckvZYnIQfgsaNkuW1EoPGC5nwkq1Nl24
=3JNA
-----END PGP SIGNATURE-----
