From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <gentoo-mips+bounces-428-garchives=archives.gentoo.org@lists.gentoo.org> Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id B9CF1138247 for <garchives@archives.gentoo.org>; Thu, 16 Jan 2014 22:29:24 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 65DFCE0C90; Thu, 16 Jan 2014 22:29:23 +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 E210BE0C90 for <gentoo-mips@lists.gentoo.org>; Thu, 16 Jan 2014 22:29:21 +0000 (UTC) Received: from [192.168.3.7] (cpe-74-77-145-97.buffalo.res.rr.com [74.77.145.97]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: blueness) by smtp.gentoo.org (Postfix) with ESMTPSA id E875633F84E for <gentoo-mips@lists.gentoo.org>; Thu, 16 Jan 2014 22:29:20 +0000 (UTC) Message-ID: <52D85D57.9010500@gentoo.org> Date: Thu, 16 Jan 2014 17:29:43 -0500 From: "Anthony G. Basile" <blueness@gentoo.org> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 Precedence: bulk List-Post: <mailto:gentoo-mips@lists.gentoo.org> List-Help: <mailto:gentoo-mips+help@lists.gentoo.org> List-Unsubscribe: <mailto:gentoo-mips+unsubscribe@lists.gentoo.org> List-Subscribe: <mailto:gentoo-mips+subscribe@lists.gentoo.org> List-Id: Gentoo Linux mail <gentoo-mips.gentoo.org> X-BeenThere: gentoo-mips@lists.gentoo.org Reply-to: gentoo-mips@lists.gentoo.org MIME-Version: 1.0 To: gentoo-mips@lists.gentoo.org Subject: Re: [gentoo-mips] On MIPS using the same CHOST for all multilib ABIs References: <20131228235839.5bb0305a@gentoo.org> <20140116210119.421c952c@pomiot.lan> <52D84994.3070306@opensource.dyc.edu> <20140116222418.6229a1b0@pomiot.lan> In-Reply-To: <20140116222418.6229a1b0@pomiot.lan> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Archives-Salt: f00e9c84-8615-4845-aa2e-b97d0900d079 X-Archives-Hash: be8a763d7edd9ddfe3d39c709a47377c On 01/16/2014 04:24 PM, Michał Górny wrote: > Dnia 2014-01-16, o godz. 16:05:24 > "Anthony G. Basile" <basile@opensource.dyc.edu> napisał(a): > >> On 01/16/2014 03:01 PM, Michał Górny wrote: >>> Dnia 2013-12-28, o godz. 23:58:39 >>> Michał Górny <mgorny@gentoo.org> napisał(a): >>> >>>> In the multilib stuff, we're using CHOST for two purposes: >>>> >>>> 1. wrapped headers are put in /usr/include/$CHOST, >>>> >>>> 2. multilib executables are prefixed with $CHOST-. >>>> >>>> (...) >>>> >>>> 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. >>> >> Mike suggested creating another variable which was a combination of >> CHOST and ABI for the multilib stuff. Why can't you pursue that approach? > Because AC_PATH_TOOL uses CHOST and some random Gentoo invention. > I got that AC_PATH_TOOL and AC_CHECK_TOOL prefix whatever utility they search for with the canonicalized chost (usually from config.guess), but I still don't see why we need this to avoid hackery? Can you give me a practial example because right now I just don't see a serious problem. -- Anthony G. Basile, Ph.D. Gentoo Linux Developer [Hardened] E-Mail : blueness@gentoo.org GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA GnuPG ID : F52D4BBA