I've had two segfaults I'd never seen before. One in sudo and one in
rdesktop. Updates later when I get things better tracked down.
--
:wq
On Wed, Apr 25, 2012 at 10:09 PM, Michael Mol wrote:
> I've had two segfaults I'd never seen before. One in sudo and one in
> rdesktop. Updates later when I get things better tracked down.
I had a gcc segfault in my atom server, with MAKEOPTS=-j5. With
MAKEOPTS=-j1, I got undefined references whi
On Wed, Apr 25, 2012 at 11:50 PM, Canek Peláez Valdés wrote:
> On Wed, Apr 25, 2012 at 10:09 PM, Michael Mol wrote:
>> I've had two segfaults I'd never seen before. One in sudo and one in
>> rdesktop. Updates later when I get things better tracked down.
>
> I had a gcc segfault in my atom server,
On Wed, Apr 25, 2012 at 11:50 PM, Canek Peláez Valdés wrote:
> On Wed, Apr 25, 2012 at 10:09 PM, Michael Mol wrote:
>> I've had two segfaults I'd never seen before. One in sudo and one in
>> rdesktop. Updates later when I get things better tracked down.
>
> I had a gcc segfault in my atom server,
On Thu, Apr 26, 2012 at 12:37 AM, Michael Mol wrote:
> On Wed, Apr 25, 2012 at 11:50 PM, Canek Peláez Valdés
> wrote:
>> On Wed, Apr 25, 2012 at 10:09 PM, Michael Mol wrote:
>>> I've had two segfaults I'd never seen before. One in sudo and one in
>>> rdesktop. Updates later when I get things be
On Thu, Apr 26, 2012 at 1:16 AM, Michael Mol wrote:
> On Thu, Apr 26, 2012 at 12:37 AM, Michael Mol wrote:
>> On Wed, Apr 25, 2012 at 11:50 PM, Canek Peláez Valdés
>> wrote:
>>> On Wed, Apr 25, 2012 at 10:09 PM, Michael Mol wrote:
I've had two segfaults I'd never seen before. One in sudo
On 04/26/2012 05:09:58 AM, Michael Mol wrote:
I've had two segfaults I'd never seen before. One in sudo and one in
rdesktop. Updates later when I get things better tracked down.
I am at glibc-2.15-r1 on AMD64 with no problems so far,
Helmut.
> Ok, yes. This version of glibc, =sys-libs/glibc-2.14.1-r3, is crud.
It's the current stable version on amd64, and you seem to be the only
one having problems with it.
I think the problem is likely with your setup (i.e. other toolchain
component, CFLAGS, ...).
> least, if you're doing parallel
On Thu, Apr 26, 2012 at 1:25 AM, Michael Mol wrote:
> On Thu, Apr 26, 2012 at 1:16 AM, Michael Mol wrote:
>> On Thu, Apr 26, 2012 at 12:37 AM, Michael Mol wrote:
>>> On Wed, Apr 25, 2012 at 11:50 PM, Canek Peláez Valdés
>>> wrote:
On Wed, Apr 25, 2012 at 10:09 PM, Michael Mol wrote:
On Thu, Apr 26, 2012 at 19:40, Michael Mol wrote:
>
> MAKEOPTS="-j1" didn't fix it. Off to find another solution.
> --
> :wq
>
Does sound like it's just you. I've been running with MAKEOPTS="-j13"
and everything compiled and ran just fine.
-- Joe
On Thu, Apr 26, 2012 at 04:47, Helmut Jarausch
wrote:
> I am at glibc-2.15-r1 on AMD64 with no problems so far,
ditto here
--
Douglas J Hunley (doug.hun...@gmail.com)
Twitter: @hunleyd Web:
douglasjhunley.com
G+: http://goo.gl/sajR3
On Thu, Apr 26, 2012 at 10:34 AM, Qian Qiao wrote:
> On Thu, Apr 26, 2012 at 19:40, Michael Mol wrote:
>>
>> MAKEOPTS="-j1" didn't fix it. Off to find another solution.
>> --
>> :wq
>>
>
> Does sound like it's just you. I've been running with MAKEOPTS="-j13"
> and everything compiled and ran just
On Thu, Apr 26, 2012 at 9:41 AM, Michael Mol 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 po
On Thu, Apr 26, 2012 at 22:41, Michael Mol wrote:
> On Thu, Apr 26, 2012 at 10:34 AM, Qian Qiao wrote:
>> On Thu, Apr 26, 2012 at 19:40, Michael Mol wrote:
>>>
>>> MAKEOPTS="-j1" didn't fix it. Off to find another solution.
>>> --
>>> :wq
>>>
>>
>> Does sound like it's just you. I've been runnin
On Thu, Apr 26, 2012 at 11:01 AM, Paul Hartman
wrote:
> On Thu, Apr 26, 2012 at 9:41 AM, Michael Mol 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 b
On Thu, Apr 26, 2012 at 7:41 AM, Michael Mol wrote:
> On Thu, Apr 26, 2012 at 10:34 AM, Qian Qiao wrote:
>> On Thu, Apr 26, 2012 at 19:40, Michael Mol wrote:
>>>
>>> MAKEOPTS="-j1" didn't fix it. Off to find another solution.
>>> --
>>> :wq
>>>
>>
>> Does sound like it's just you. I've been runn
On Thu, Apr 26, 2012 at 11:27 AM, Mark Knecht wrote:
> On Thu, Apr 26, 2012 at 7:41 AM, Michael Mol wrote:
>> On Thu, Apr 26, 2012 at 10:34 AM, Qian Qiao wrote:
>>> On Thu, Apr 26, 2012 at 19:40, Michael Mol wrote:
MAKEOPTS="-j1" didn't fix it. Off to find another solution.
--
>>
On Thu, Apr 26, 2012 at 11:53 AM, Michael Mol wrote:
> On Thu, Apr 26, 2012 at 11:27 AM, Mark Knecht wrote:
>> On Thu, Apr 26, 2012 at 7:41 AM, Michael Mol wrote:
>>> On Thu, Apr 26, 2012 at 10:34 AM, Qian Qiao wrote:
On Thu, Apr 26, 2012 at 19:40, Michael Mol wrote:
>
> MAKEOPTS=
On Thu, Apr 26, 2012 at 2:20 PM, Canek Peláez Valdés wrote:
> On Thu, Apr 26, 2012 at 11:53 AM, Michael Mol wrote:
>> On Thu, Apr 26, 2012 at 11:27 AM, Mark Knecht wrote:
>>> On Thu, Apr 26, 2012 at 7:41 AM, Michael Mol wrote:
On Thu, Apr 26, 2012 at 10:34 AM, Qian Qiao wrote:
> On Th
On Thu, Apr 26, 2012 at 2:26 PM, Michael Mol wrote:
> On Thu, Apr 26, 2012 at 2:20 PM, Canek Peláez Valdés wrote:
>> On Thu, Apr 26, 2012 at 11:53 AM, Michael Mol wrote:
>>> On Thu, Apr 26, 2012 at 11:27 AM, Mark Knecht wrote:
On Thu, Apr 26, 2012 at 7:41 AM, Michael Mol wrote:
> On T
Am Mittwoch, 25. April 2012, 22:50:53 schrieb Canek Peláez Valdés:
> On Wed, Apr 25, 2012 at 10:09 PM, Michael Mol wrote:
> > I've had two segfaults I'd never seen before. One in sudo and one in
> > rdesktop. Updates later when I get things better tracked down.
>
> I had a gcc segfault in my atom
Am Donnerstag, 26. April 2012, 12:53:28 schrieb Michael Mol:
> On Thu, Apr 26, 2012 at 11:27 AM, Mark Knecht wrote:
> > On Thu, Apr 26, 2012 at 7:41 AM, Michael Mol wrote:
> >> On Thu, Apr 26, 2012 at 10:34 AM, Qian Qiao wrote:
> >>> On Thu, Apr 26, 2012 at 19:40, Michael Mol wrote:
> MAKE
> #expanded form of -march=native. Nothing special here. Noting this
> here because people keep freaking out when they see it in-line.
> SYS_CFLAGS_MARCH_NATIVE_EXP="-march=amdfam10 -mcx16 -msahf -mpopcnt
> --param l1-cache-size=64 --param l1-cache-line-size=64 --param
> l2-cache-size=512 -mtune=am
On Thu, Apr 26, 2012 at 8:35 PM, Adam Carter wrote:
>> #expanded form of -march=native. Nothing special here. Noting this
>> here because people keep freaking out when they see it in-line.
>> SYS_CFLAGS_MARCH_NATIVE_EXP="-march=amdfam10 -mcx16 -msahf -mpopcnt
>> --param l1-cache-size=64 --param l1
On Thu, Apr 26, 2012 at 10:38:21AM -0400, Penguin Lover Doug Hunley squawked:
> On Thu, Apr 26, 2012 at 04:47, Helmut Jarausch
> wrote:
> > I am at glibc-2.15-r1 on AMD64 with no problems so far,
>
> ditto here
>
Hey guys, I think we've pretty much established that Michael is
running into an is
From: Michael Mol [mailto:mike...@gmail.com]
Sent: Thursday, April 26, 2012 9:54 PM
> I can no longer ssh into either inara or kaylee.
Clearly they are busy fsck'ing /malcom and /simon
On Apr 27, 2012 8:58 AM, "Michael Mol" wrote:
>
> On Thu, Apr 26, 2012 at 8:35 PM, Adam Carter
wrote:
> >> #expanded form of -march=native. Nothing special here. Noting this
> >> here because people keep freaking out when they see it in-line.
> >> SYS_CFLAGS_MARCH_NATIVE_EXP="-march=amdfam10 -mcx
I don't think I have one on kaylee. If I have one on inara, it'd be >=
system RAM, so at least 4G.
On Apr 28, 2012 3:14 AM, "Pandu Poluan" wrote:
>
> On Apr 27, 2012 8:58 AM, "Michael Mol" wrote:
> >
> > On Thu, Apr 26, 2012 at 8:35 PM, Adam Carter
> wrote:
> > >> #expanded form of -march=nativ
On Apr 28, 2012 3:32 PM, "Michael Mol" wrote:
>
> On Apr 28, 2012 3:14 AM, "Pandu Poluan" wrote:
>>
>8 snip
>>
>> How big is your swapfile?
>>
>> Rgds,
>
> I don't think I have one on kaylee. If I have one on inara, it'd be >=
system RAM, so at least 4G.
Are you sure?
I remember having a
Kaylee has 10GB of RAM...if that's not enough, I'll be disabling graphite.
(Though I haven't explicitly enabled it, either.)
But, no I'm not sure, and can't check until Sunday eveningish. Currently at
Penguicon.
On Apr 28, 2012 5:32 AM, "Pandu Poluan" wrote:
>
> On Apr 28, 2012 3:32 PM, "Michael
On Sat, Apr 28, 2012 at 11:07 AM, Michael Mol wrote:
> Kaylee has 10GB of RAM...if that's not enough, I'll be disabling graphite.
> (Though I haven't explicitly enabled it, either.)
>
> But, no I'm not sure, and can't check until Sunday eveningish. Currently at
> Penguicon.
Wow. Just wow. This is
On Sat, Jun 02, 2012 at 10:52:12PM -0400, Michael Mol wrote:
> On Sat, Apr 28, 2012 at 11:07 AM, Michael Mol wrote:
> Wow. Just wow. This is incredible.
>
> This is repeatable for me.
>
> * The problem occurred while executing the ebuild file named
> * 'glibc-2.14.1-r3.ebuild' located in the
On Sat, Jun 2, 2012 at 11:34 PM, Dmitry Goncharov
wrote:
> On Sat, Jun 02, 2012 at 10:52:12PM -0400, Michael Mol wrote:
>> On Sat, Apr 28, 2012 at 11:07 AM, Michael Mol wrote:
>> Wow. Just wow. This is incredible.
>>
>> This is repeatable for me.
>>
>
>> * The problem occurred while executing t
On Sat, Jun 02, 2012 at 11:56:01PM -0400, Michael Mol wrote:
> On Sat, Jun 2, 2012 at 11:34 PM, Dmitry Goncharov
> wrote:
> > On Sat, Jun 02, 2012 at 10:52:12PM -0400, Michael Mol wrote:
> >> On Sat, Apr 28, 2012 at 11:07 AM, Michael Mol wrote:
> >> Wow. Just wow. This is incredible.
> >>
> >> Th
On Sun, Jun 3, 2012 at 12:08 AM, Dmitry Goncharov
wrote:
> On Sat, Jun 02, 2012 at 11:56:01PM -0400, Michael Mol wrote:
>> On Sat, Jun 2, 2012 at 11:34 PM, Dmitry Goncharov
>> wrote:
>> > On Sat, Jun 02, 2012 at 10:52:12PM -0400, Michael Mol wrote:
>> >> On Sat, Apr 28, 2012 at 11:07 AM, Michael
On Sat, Jun 2, 2012 at 11:56 PM, Michael Mol wrote:
> On Sat, Jun 2, 2012 at 11:34 PM, Dmitry Goncharov
> wrote:
>> On Sat, Jun 02, 2012 at 10:52:12PM -0400, Michael Mol wrote:
>>> On Sat, Apr 28, 2012 at 11:07 AM, Michael Mol wrote:
>>> Wow. Just wow. This is incredible.
>>>
>>> This is repeata
On Sat, Jun 23, 2012 at 12:37 AM, Michael Mol wrote:
> On Sat, Jun 2, 2012 at 11:56 PM, Michael Mol wrote:
>> On Sat, Jun 2, 2012 at 11:34 PM, Dmitry Goncharov
>> wrote:
>>> On Sat, Jun 02, 2012 at 10:52:12PM -0400, Michael Mol wrote:
On Sat, Apr 28, 2012 at 11:07 AM, Michael Mol wrote:
>>
On Sat, Jun 23, 2012 at 6:08 PM, Michael Mol wrote:
> https://bugs.gentoo.org/show_bug.cgi?id=423149
As it turned out, it was my CFLAGS. Not the ones anyone usually cares
about, either.
If you build glibc with CFLAGS="${CFLAGS} -g3", your glibc will be
very, very broken. Apparently, it's old, kn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27.06.2012 15:58, Michael Mol wrote:
>
> The other big thing I kept hearing about was "try changing
> {this|that|other thing}; it might be affecting glibc, because glibc
> is a whiny b*tch". Are there alternatives to glibc?
>
Alternatives? Har
On Wed, 27 Jun 2012 09:58:57 -0400, Michael Mol wrote:
> If you build glibc with CFLAGS="${CFLAGS} -g3", your glibc will be
> very, very broken. Apparently, it's old, known and has been a problem
> for about five years.[1]
Thisd sounds worthy of a bug report, an ebuild allowing you to break
somet
On Wed, Jun 27, 2012 at 8:58 AM, Michael Mol wrote:
> On Sat, Jun 23, 2012 at 6:08 PM, Michael Mol wrote:
>> https://bugs.gentoo.org/show_bug.cgi?id=423149
>
> As it turned out, it was my CFLAGS. Not the ones anyone usually cares
> about, either.
>
> If you build glibc with CFLAGS="${CFLAGS} -g3"
On Wed, Jun 27, 2012 at 12:12 PM, Neil Bothwick wrote:
> On Wed, 27 Jun 2012 09:58:57 -0400, Michael Mol wrote:
>
>> If you build glibc with CFLAGS="${CFLAGS} -g3", your glibc will be
>> very, very broken. Apparently, it's old, known and has been a problem
>> for about five years.[1]
>
> Thisd sou
On Wed, 27 Jun 2012 12:45:13 -0400, Michael Mol wrote:
> Also, even if the ebuild issued a warning, there's no guarantee the
> warning would ever be made visible; the system is well and truly hosed
> before the 'postinst' stage of the install, so who knows whether or
> not the cache-and-show-later
On Wed, Jun 27, 2012 at 1:05 PM, Neil Bothwick wrote:
> On Wed, 27 Jun 2012 12:45:13 -0400, Michael Mol wrote:
>
>> Also, even if the ebuild issued a warning, there's no guarantee the
>> warning would ever be made visible; the system is well and truly hosed
>> before the 'postinst' stage of the in
44 matches
Mail list logo
