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: firefox-bin crashing a few times every day
Date: Mon, 29 Oct 2007 23:45:28 +0000 (UTC)	[thread overview]
Message-ID: <pan.2007.10.29.23.45.28@cox.net> (raw)
In-Reply-To: d257c3560710291145p65425e7ao9a55c53484ccaf0f@mail.gmail.com

Beso <givemesugarr@gmail.com> posted
d257c3560710291145p65425e7ao9a55c53484ccaf0f@mail.gmail.com, excerpted
below, on  Mon, 29 Oct 2007 19:45:52 +0100:

> i'd suggest you install ccache before compiling if you don't yet use it
> and to add the option --buildpkg to emerge, so that you can have the
> firefox package built for your particular system. this is useful also
> for long time compiling packages as gtk+,qt or kdelibs and kdebase. if
> you'd later need to reinstall them (for example the expat-2 update) you
> can install them in a matter of little time. just be aware that the
> packaging requires additional disk space to package the files once
> they're compiled. i didn't experience crashes in the last 6 months.

I have FEATURES=ccache and buildpkg both on, so no need to add the emerge 
parameter, but yes, I've been doing this for some time, and seriously 
recommend it (particularly the buildpkg part, ccache is covered in the 
handbook reasonably well already) myself.

-- 
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:[~2007-10-29 23:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29 17:34 [gentoo-amd64] firefox-bin crashing a few times every day Mark Knecht
2007-10-29 17:41 ` Javi Moreno
2007-10-29 17:48   ` Mark Knecht
2007-10-29 18:45     ` Beso
2007-10-29 23:45       ` Duncan [this message]
2007-10-30  0:02       ` Mark Knecht
2007-11-11 21:49       ` Mark Knecht
2007-11-11 22:52         ` Beso
2007-11-11 23:05           ` Mark Knecht
2007-11-12  8:36             ` Beso
2007-11-12 17:14               ` Jeffrey Gardner
2007-11-12 18:35               ` Mark Knecht
2007-11-12 18:56                 ` Beso
2007-11-12 19:25                   ` Mark Knecht
2007-11-12 21:02                     ` Beso
2007-11-12 19:32                 ` Drake Donahue
2007-11-12 21:03                   ` Mark Knecht
2007-11-12 21:23                     ` Beso
2007-11-12 22:50                       ` Mark Knecht
2007-11-12 22:46                     ` Drake Donahue
2007-11-13  1:31                       ` nuitari
2007-11-12 21:09                   ` Beso
2007-11-12 19:39               ` Sergio Polini
2007-11-12 21:06                 ` Beso
2007-11-13  0:35                   ` Mark Knecht
2007-11-13  3:03                     ` Drake Donahue
2007-11-13 17:30                     ` [gentoo-amd64] " Duncan
2007-11-13 17:55                       ` Mark Knecht

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=pan.2007.10.29.23.45.28@cox.net \
    --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