From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] x32 changing CHOST
Date: Fri, 31 Aug 2012 14:19:47 -0400 [thread overview]
Message-ID: <CAJaTeTosDDy+qxjLKfSUWzkKPK8cqnsKZvaF9Ze=b0PVyp05jw@mail.gmail.com> (raw)
In-Reply-To: <201208172338.57193.vapier@gentoo.org>
On Fri, Aug 17, 2012 at 11:38 PM, Mike Frysinger wrote:
> people seem to be settling on x86_64-pc-linux-gnux32 as the default tuple, so
> i'll be updating our profiles to use that by default. this shouldn't impact
> anyone already running x32 as the existing tuple/ABI settings should continue
> to work just fine (no plans to ever change that).
i've finally gotten around to pushing this. i did an in-place upgrade
in my chroot and it worked fine.
-mike
prev parent reply other threads:[~2012-08-31 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 3:38 [gentoo-dev] x32 changing CHOST Mike Frysinger
2012-08-31 18:19 ` Mike Frysinger [this message]
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='CAJaTeTosDDy+qxjLKfSUWzkKPK8cqnsKZvaF9Ze=b0PVyp05jw@mail.gmail.com' \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.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