From: "Michał Górny" <mgorny@gentoo.org>
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
Date: Thu, 16 Jan 2014 21:01:19 +0100 [thread overview]
Message-ID: <20140116210119.421c952c@pomiot.lan> (raw)
In-Reply-To: <20131228235839.5bb0305a@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
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.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
next prev parent reply other threads:[~2014-01-16 20:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 22:58 [gentoo-mips] On MIPS using the same CHOST for all multilib ABIs Michał Górny
2013-12-28 23:55 ` Markos Chandras
2013-12-29 2:12 ` Mike Frysinger
[not found] ` <20131229163354.35b65df5@gentoo.org>
2013-12-29 18:21 ` Mike Frysinger
2013-12-30 9:44 ` Michał Górny
2013-12-29 21:40 ` [gentoo-mips] " Joshua Kinard
2013-12-29 21:48 ` Markos Chandras
2013-12-29 21:48 ` Michał Górny
2013-12-29 21:48 ` Markos Chandras
2013-12-29 21:52 ` Anthony G. Basile
2013-12-29 22:04 ` Michał Górny
2013-12-29 23:56 ` Mike Frysinger
2013-12-30 7:51 ` Mike Frysinger
2013-12-30 8:17 ` sébastien bertoletto
2013-12-29 22:13 ` Markos Chandras
2013-12-29 22:19 ` Anthony G. Basile
2013-12-29 22:33 ` Markos Chandras
2013-12-29 23:47 ` Anthony G. Basile
2014-01-16 20:01 ` Michał Górny [this message]
2014-01-16 21:05 ` [gentoo-mips] " Anthony G. Basile
2014-01-16 21:24 ` Michał Górny
2014-01-16 22:29 ` Anthony G. Basile
2014-01-17 4:47 ` Michał Górny
2014-01-17 18:20 ` Markos Chandras
2014-01-17 18:36 ` Matt Turner
2014-01-17 19:38 ` Markos Chandras
2014-01-17 21:57 ` Matt Turner
2014-01-17 18:51 ` Michał Górny
2014-01-17 19:44 ` Markos Chandras
2014-01-21 20:52 ` Markos Chandras
2014-01-22 14:24 ` Anthony G. Basile
2014-01-22 14:38 ` Michał Górny
2014-01-22 20:39 ` Markos Chandras
2014-01-22 21:07 ` Anthony G. Basile
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140116210119.421c952c@pomiot.lan \
--to=mgorny@gentoo.org \
--cc=gentoo-mips@lists.gentoo.org \
--cc=mips@gentoo.org \
--cc=multilib@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox