From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Just a heads-up, I think =sys-libs/glibc-2.14.1-r3 is a stinker.
Date: Thu, 26 Apr 2012 10:01:31 -0500 [thread overview]
Message-ID: <CAEH5T2Pa3bX8bXhUyRGo4TRRge+105G-D-nFakc+8dfPd7VbdA@mail.gmail.com> (raw)
In-Reply-To: <CA+czFiDVxnHPYAGmr7cpudyZE-g9p=iLaRCCutv7H_AteJkh1w@mail.gmail.com>
On Thu, Apr 26, 2012 at 9:41 AM, Michael Mol <mikemol@gmail.com> wrote:
> Checking to see if it's a distcc problem, now. If it is, it'll only be
> the third time I've ever had issues from distcc, and the first time a
> distcc issue resulted in a successful build of a package that broke
> things.
Just to cover all possibilities... since everyone else is saying it's
not a problem for them -- have you run a memory test?
next prev parent reply other threads:[~2012-04-26 15:03 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 3:09 [gentoo-user] Just a heads-up, I think =sys-libs/glibc-2.14.1-r3 is a stinker Michael Mol
2012-04-26 3:50 ` Canek Peláez Valdés
2012-04-26 4:10 ` Michael Mol
2012-04-26 4:37 ` Michael Mol
2012-04-26 5:16 ` Michael Mol
2012-04-26 5:25 ` Michael Mol
2012-04-26 11:40 ` Michael Mol
2012-04-26 14:34 ` Qian Qiao
2012-04-26 14:41 ` Michael Mol
2012-04-26 15:01 ` Paul Hartman [this message]
2012-04-26 15:24 ` Michael Mol
2012-04-26 15:04 ` Qian Qiao
2012-04-26 15:27 ` Mark Knecht
2012-04-26 16:53 ` Michael Mol
2012-04-26 18:20 ` Canek Peláez Valdés
2012-04-26 18:26 ` Michael Mol
2012-04-26 19:06 ` Michael Mol
2012-04-26 20:35 ` Volker Armin Hemmann
2012-04-27 0:35 ` Adam Carter
2012-04-27 1:53 ` Michael Mol
2012-04-27 16:23 ` Mike Edenfield
2012-04-28 7:10 ` Pandu Poluan
2012-04-28 8:25 ` Michael Mol
2012-04-28 9:28 ` Pandu Poluan
2012-04-28 15:07 ` Michael Mol
2012-06-03 2:52 ` Michael Mol
2012-06-03 3:34 ` Dmitry Goncharov
2012-06-03 3:56 ` Michael Mol
2012-06-03 4:08 ` Dmitry Goncharov
2012-06-03 4:15 ` Michael Mol
2012-06-23 4:37 ` Michael Mol
2012-06-23 22:08 ` Michael Mol
2012-06-27 13:58 ` [SOLVED] " Michael Mol
2012-06-27 14:35 ` Hinnerk van Bruinehsen
2012-06-27 16:12 ` Neil Bothwick
2012-06-27 16:45 ` Michael Mol
2012-06-27 17:05 ` Neil Bothwick
2012-06-27 17:13 ` Michael Mol
2012-06-27 16:38 ` Paul Hartman
2012-04-26 10:51 ` Andrea Conti
2012-04-26 20:30 ` Volker Armin Hemmann
2012-04-26 7:01 ` [gentoo-user] " Nikos Chantziaras
2012-04-26 7:17 ` Dale
2012-04-26 10:06 ` napalm
2012-04-26 8:47 ` [gentoo-user] " Helmut Jarausch
2012-04-26 14:38 ` Doug Hunley
2012-04-27 9:20 ` Willie WY Wong
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=CAEH5T2Pa3bX8bXhUyRGo4TRRge+105G-D-nFakc+8dfPd7VbdA@mail.gmail.com \
--to=paul.hartman+gentoo@gmail.com \
--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