From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: firefox-bin optimizations?
Date: Thu, 07 Oct 2010 15:59:42 +0800 [thread overview]
Message-ID: <1286438382.25943.61.camel@rattus> (raw)
In-Reply-To: <1286437948.25943.59.camel@rattus>
To clarify, building everything except gcc works fine - its gcc itself
thats problematic
BillK
On Thu, 2010-10-07 at 15:52 +0800, William Kenworthy wrote:
> In /etc/fstab I have (this is a diskless atom based PXE system):
>
> shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
>
> tmpfs /tmp tmpfs size=1250M,mode=1777,noatime,auto 0 0
> tmpfs /var/lock tmpfs size=10m,noatime,auto 0 0
> tmpfs /var/run tmpfs size=10m,noatime,auto 0 0
> tmpfs /var/cache/hald tmpfs size=10m,noatime,auto 0 0
>
>
> and in /etc/conf.d/local.start:
> mkdir /tmp/portage
> mkdir /tmp/portage/tmp
> mkdir /tmp/portage/distfiles
>
> and it /etc/make.conf
>
> DISTDIR="/tmp/portage/distfiles"
> PORTAGE_TMPDIR='/tmp/portage/tmp'
> PORTDIR='/tmp/portage/'
> PORTDIR_OVERLAY="/usr/local/portage"
> PORTAGE_BINHOST="http://tinderbox.dev.gentoo.org/default-linux/amd64/"
> PKGDIR="/tmp/portage/packages/"
>
>
> It works fine except for gcc where with 3G of ram, everything in tmpfs
> and swap over nfs works randomly due to running out of ram.
>
> BillK
>
>
>
>
> On Thu, 2010-10-07 at 00:55 -0400, Walter Dnes wrote:
> > On Tue, Oct 05, 2010 at 11:27:54PM -0400, Walter Dnes wrote
> >
> > > Looks like I can tweak stuff in the ebuild via "mozconfig_annotate"
> > > lines, and then...
> > >
> > > ebuild firefox-3.6.9.ebuild manifest
> > > emerge firefox
> >
> > Something isn't working. I put in
> > mozconfig_annotate '' --disable-pango
> > mozconfig_annotate '' --disable-oji --disable-mathml
> >
> > into the ebuild (a copy in my local overlay) and ebuild-manifested it.
> > Portage said it was building from the overlay, but "about:buildconfig"
> > shows them as being enabled. I have been able to
> > --disable-necko-wifi (WTF is *THAT* in a browser, fercryingoutloud?).
> >
> > Any ideas? A long time ago, in a place far away, I used to build
> > Mozilla 0.9x "the hard way", because the downloadable binary was
> > painfully slow on my machine. And later on Phoenix 0.9x (remember
> > that?). I've forgotten most of what I learned, but I can follow the
> > instructions at https://developer.mozilla.org/En/Simple_Firefox_build
> > I have a couple of questions before proceeding...
> > 1) what do I have to set to force all files to be installed in /opt or
> > in /usr/local ?
> > 2) I've got 8 gigs of ram. How do I force the compiler to use /dev/shm
> > as the scratch directory ?
> >
>
--
William Kenworthy <billk@iinet.net.au>
Home in Perth!
next prev parent reply other threads:[~2010-10-07 8:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 10:58 [gentoo-user] firefox-bin optimizations? Mark David Dumlao
2010-09-30 12:00 ` Johannes Kimmel
2010-09-30 12:30 ` Mark David Dumlao
2010-09-30 19:37 ` [gentoo-user] " walt
2010-09-30 20:36 ` Mark David Dumlao
2010-10-05 5:49 ` Walter Dnes
2010-10-05 13:12 ` Bill Longman
2010-10-05 15:16 ` walt
2010-10-06 3:27 ` Walter Dnes
2010-10-07 4:55 ` Walter Dnes
2010-10-07 7:52 ` William Kenworthy
2010-10-07 7:59 ` William Kenworthy [this message]
2010-10-07 9:03 ` Arttu V.
2010-10-09 5:17 ` Walter Dnes
2010-10-09 15:53 ` Arttu V.
2010-10-12 3:19 ` Walter Dnes
2010-10-14 4:12 ` Walter Dnes
2010-10-14 14:21 ` Paul Hartman
2010-10-09 15:54 ` Peter Weilbacher
2010-10-09 15:48 ` Peter Weilbacher
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=1286438382.25943.61.camel@rattus \
--to=billk@iinet.net.au \
--cc=gentoo-user@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