public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] glibc-2.3.4.20041102-r1 has gone goofy
Date: Wed, 23 Mar 2005 23:53:40 +0200	[thread overview]
Message-ID: <1111614820.2513.2.camel@nosferatu.lan> (raw)
In-Reply-To: <200503231411.20959.lostson@lostsonsvault.org>

[-- Attachment #1: Type: text/plain, Size: 969 bytes --]

On Wed, 2005-03-23 at 14:11 +0000, LostSon wrote:
> On Wednesday 23 March 2005 05:10 pm, Aron Griffis wrote:
> > LostSon wrote:        [Tue Mar 22 2005, 07:44:38PM EST]
> >
> > > This had been brought to my attention earlier and my laptop's time
> and
> > > date is set right. Unfortunately this doesnt help either.
> >
> > http://bugs.gentoo.org/show_bug.cgi?id=37958
> >
> > --
> > Aron Griffis
> > Gentoo Linux Developer
> 
> -- 
>  Ok i read through that bug and have followed its suggestions
> recompiled my 
> gcc. Made sure my time was correct and its still looping away. Maybe
> its just 
> time for a fresh install or something. I have to have my laptop in
> good 
> working order. Seriously discouraged.
> 

Not very scientific, but try:

  $ touch foo; find / -newer foo

maybe its not a header from gcc that is newer ?


-- 
Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-03-23 21:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-23  0:27 [gentoo-dev] glibc-2.3.4.20041102-r1 has gone goofy LostSon
2005-03-23  6:24 ` Mike Frysinger
2005-03-23  0:44   ` LostSon
2005-03-23 17:10     ` Aron Griffis
2005-03-23 14:11       ` LostSon
2005-03-23 21:53         ` Martin Schlemmer [this message]
2005-03-23 16:02           ` LostSon

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=1111614820.2513.2.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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