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 6EB73138247 for ; Thu, 16 Jan 2014 20:01:36 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0FA4FE0BFE; Thu, 16 Jan 2014 20:01:35 +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 88570E0BFE for ; Thu, 16 Jan 2014 20:01:34 +0000 (UTC) Received: from pomiot.lan (static-81-219-166-219.devs.futuro.pl [81.219.166.219]) (using SSLv3 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 69AE833F439; Thu, 16 Jan 2014 20:01:32 +0000 (UTC) Date: Thu, 16 Jan 2014 21:01:19 +0100 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-mips@lists.gentoo.org Cc: mips@gentoo.org, multilib@gentoo.org Subject: Re: [gentoo-mips] On MIPS using the same CHOST for all multilib ABIs Message-ID: <20140116210119.421c952c@pomiot.lan> In-Reply-To: <20131228235839.5bb0305a@gentoo.org> References: <20131228235839.5bb0305a@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-mips@lists.gentoo.org Reply-to: gentoo-mips@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/wwvtkr8CUbfiiS/6ljW37fg"; protocol="application/pgp-signature" X-Archives-Salt: e61287a7-6836-45ec-828d-044088a3bfb2 X-Archives-Hash: 441655e881777dfa1893724690e33d57 --Sig_/wwvtkr8CUbfiiS/6ljW37fg Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dnia 2013-12-28, o godz. 23:58:39 Micha=C5=82 G=C3=B3rny napisa=C5=82(a): > In the multilib stuff, we're using CHOST for two purposes: >=20 > 1. wrapped headers are put in /usr/include/$CHOST, >=20 > 2. multilib executables are prefixed with $CHOST-. >=20 > (...) >=20 > I'd suggest that you changed the CHOST values to uniquely identify ABI > in use, at least in multilib profiles and preferably in all of them. Ping. The discussion seems stalled while we're hitting increasing number of packages that rely on CHOST to run *-config programs. My main is that AFAICS this is the only upstream-compatible way of handling this without hackery on our side. As far as I understand, if you changed the CHOSTs only for non-native ABIs (and therefore leaving the prefix used for toolchain unchanged) the risk should be minimal. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/wwvtkr8CUbfiiS/6ljW37fg Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQJ8BAEBCgBmBQJS2DqVXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2REJCMDdDQzRGMERBRDA2RUEwQUZFNDFC MDdBMUFFQUVGQjQ0NjRFAAoJELB6GurvtEZOXmAP/Re2Phv0H7GFh6qoGpVn+dHZ zL65KIi6+EOBI03Vj8/LoVit1Oyba0ZYglnqd7P57qH9cU/OwSzZzuY7QeK7VDwy KuGgH6ja+1FTmy2GC1ac07mUGW0NPuoScXCTIn9vuagtDSZJz8MGH2200d01IIeE gM7mUVUnpCQSUT/hKWXKSakfKe5suV3mBIRUSd/DaqGNFfMi8WZvgK1wqsQdfHQR q6AI1dqyPEqYjkOvRtTpHLmrmxm73E+SsMdsLkdf71U3BI1BlXTB2leFUuJI2yCM HfGf1AaCT/jgJThDU4JBcY4PuI8ktIG7OKM/SmpbM1WIAeoOafRGq17S6JAC/eU7 TCJ+CtLBIXswCTZ0nRCKn0pS3o999pKI0HNjci4S/EDHk94VtjNXd59hX/ZAeJQf DiOhyyktr36JzTKmIxej555Ny3Tz1DGpc0FMTi7fGvW0ViSlRvKXkjyugxqolmWQ V7gKQkMiCotR2l+fJF6AfdQ249SvUPsuk3TWpzB5ICCjC7AZsVsKEhAvADGI2G0j MtDWCuu1TfEXoIKkq4o6KwBidKoIWKM/JrlTVsQELrZj6xJK8s7K3b5owrFrs5s7 9bQh6eKEydbA1jTRc0XoEICr7hiy8+d3NLaeRrEPD8snsIxwjZsBkR6x9bLeewq5 ENDRkNrDr/f/WmXcXayM =gQlA -----END PGP SIGNATURE----- --Sig_/wwvtkr8CUbfiiS/6ljW37fg--