public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: Browsing speed problems - possibly flash related
Date: Fri, 29 Dec 2006 12:49:06 +0000 (UTC)	[thread overview]
Message-ID: <en32s2$a9f$2@sea.gmane.org> (raw)
In-Reply-To: 200612281559.21743.bss03@volumehost.net

"Boyd Stephen Smith Jr." <bss03@volumehost.net> posted
200612281559.21743.bss03@volumehost.net, excerpted below, on  Thu, 28 Dec
2006 15:59:15 -0600:

> On Thursday 28 December 2006 10:01, "Mark Knecht" <markknecht@gmail.com>
> wrote about '[gentoo-amd64] Browsing speed problems - possibly flash
> related':
>>    Is this a firefox-bin thing? Maybe I should build firefox from
>> source?
> 
> Good luck getting flash to work if you do that. :P

Oh, it should be no problem, as long as one is building a 32-bit firefox,
presumably in one's 32-bit chroot, following the Gentoo/amd64 32-bit
chroot guide.

Of course, if one is building a standard 64-bit firefox and expecting the
32-bit flash shared object plugin to work in the 64-bit firefox process
address space, then one is in for a bit of disappointment, but that's only
common sense so should be expected and go without saying. =8^P

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2006-12-29 12:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-28 16:01 [gentoo-amd64] Browsing speed problems - possibly flash related Mark Knecht
2006-12-28 21:59 ` Boyd Stephen Smith Jr.
2006-12-29 12:49   ` Duncan [this message]
2006-12-29 13:31     ` [gentoo-amd64] " Wil Reichert
2006-12-29 22:45       ` Mark Knecht
2006-12-29 23:42         ` Duncan
2006-12-30 16:56           ` Harry Holt
2007-01-01  4:26         ` Drake Donahue

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='en32s2$a9f$2@sea.gmane.org' \
    --to=1i5t5.duncan@cox.net \
    --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