From: "David M. Fellows" <fellows@unb.ca>
To: <gentoo-amd64@lists.gentoo.org>
Subject: Re: [gentoo-amd64] Re: Did devs change phonon flags without rev'ing package?
Date: Tue, 31 Mar 2015 16:43:13 -0300 [thread overview]
Message-ID: <CY1PR0401MB11941FA2F71EF62901B167AAC7F40@CY1PR0401MB1194.namprd04.prod.outlook.com> (raw)
In-Reply-To: <20150331164044.GC26091@crud>
On Tue, 31 Mar 2015 11:40:44 -0500
Barry Schwartz wrote -
> Duncan <1i5t5.duncan@cox.net> skribis:
> > > Is it still necessary to be using multilib?
> >
> > If you're running 100% freedomware, almost certainly not ...
>
> Firefox binaries are 32-bit. QED.
More accurately:
32-bit Firefox binaries are 32 bit
64-bit Firefox binaries are 64 bit
From firefox-bin-35.0.ebuild (others are similar):
SRC_URI="${SRC_URI}
amd64? ( ${MOZ_FTP_URI}/${MOZ_PV}/linux-x86_64/en-US/${MOZ_P}.tar.bz2 -> ${PN}_x86_64-${PV}.tar.bz2 )
x86? ( ${MOZ_FTP_URI}/${MOZ_PV}/linux-i686/en-US/${MOZ_P}.tar.bz2 -> ${PN}_i686-${PV}.tar.bz2 )"
QED.
>
> (I rarely run Firefox binaries or even keep them installed, but it
> does occasionally happen.)
>
Dave F
next prev parent reply other threads:[~2015-03-31 19:43 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 [this message]
2015-04-01 0:28 ` Duncan
2015-04-01 0:47 ` I can run 32-bit stuff and you can't (was Re: [gentoo-amd64] Re: Did devs change phonon flags without rev'ing package?) Barry Schwartz
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=CY1PR0401MB11941FA2F71EF62901B167AAC7F40@CY1PR0401MB1194.namprd04.prod.outlook.com \
--to=fellows@unb.ca \
--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