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 <bi...@iinet.net.au>
Home in Perth!


Reply via email to