public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Barry Schwartz <chemoelectric@chemoelectric.org>
To: gentoo-amd64@lists.gentoo.org
Subject: I can run 32-bit stuff and you can't (was Re: [gentoo-amd64] Re: Did devs change phonon flags without rev'ing package?)
Date: Tue, 31 Mar 2015 19:47:47 -0500	[thread overview]
Message-ID: <20150401004747.GA19719@crud> (raw)
In-Reply-To: <pan$5cbb8$7a7b6a03$392b06c0$8eb2e220@cox.net>

I expected quibbling on the ‘need’ to run a 32-bit binary. Fact is,
‘need’ is up to the user, and not up to others. If you want to install
the main Firefox binary it is 32-bit; and that’s just one
example. Substitute any software name you like in there, as a 32-bit
binary; the hardware can run it. Only software can prevent that.

As I say, the distinction is mainly due to Gentoo having botched
multilib support on AMD64. We should have stuck with the original
layout, whereby there was no profile distinction and everything 64-bit
went in lib. There should be no need to install 32-bit toolchain if
you do not want it, regardless of a profile supporting multilib.



      reply	other threads:[~2015-04-01  0:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 19:15 [gentoo-amd64] Did devs change phonon flags without rev'ing package? Mark Knecht
2015-03-30 19:48 ` Volker Armin Hemmann
2015-03-30 21:04 ` Frank Peters
2015-03-30 21:26   ` Mark Knecht
2015-03-30 22:10     ` Barry Schwartz
2015-03-30 22:23       ` Mark Knecht
2015-03-30 23:06         ` Barry Schwartz
2015-03-31  5:02   ` [gentoo-amd64] " Duncan
2015-03-31  7:32     ` Frank Peters
2015-03-31 16:40     ` Barry Schwartz
2015-03-31 19:43       ` David M. Fellows
2015-04-01  0:28         ` Duncan
2015-04-01  0:47           ` Barry Schwartz [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=20150401004747.GA19719@crud \
    --to=chemoelectric@chemoelectric.org \
    --cc=gentoo-amd64@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